Control the back, menu and home button

How do i control the back, menu and home buttons?

I want my application to have a menu that comes forth when i pres “Menu” and i want the application to go back if i press the back button, not out of the program. [import]uid: 28895 topic_id: 6352 reply_id: 306352[/import]

+1

also any way to get feedback from a physical keyboard or d-pad? [import]uid: 8872 topic_id: 6352 reply_id: 22088[/import]

+1

This is a huge usability issue. I did some user testing with a player…and this person naturally thought that the back button would take them to the previous screen. Having it exit confused them.

For now, one solution may be to have a back button image in the game/app itself.

[import]uid: 12700 topic_id: 6352 reply_id: 22142[/import]

Thanks for your input. This is currently filed as case #744 in our internal bug base.

Tim [import]uid: 8196 topic_id: 6352 reply_id: 23088[/import]

I’m happy to hear this is being worked on! This is a really big deal for Android development since the Home/Back/Menu/Search buttons are part of the spec defining Android. Not being able to respond to all of them correctly is huge.

I haven’t subscribed yet but the “daily builds” could make me subscribe that much sooner - if I knew what kind of stuff was showing up there. Is #744 being worked on and making it into the builds or is it really far down on the list? I’d love to be able to see what kinds of things are coming up. [import]uid: 39515 topic_id: 6352 reply_id: 25540[/import]

Can you see this page?

http://developer.anscamobile.com/content/corona-daily-builds/summary

Its a summary of the updates per build upto 280. We’re at 307 now [import]uid: 8872 topic_id: 6352 reply_id: 25541[/import]

Thanks, @kam187, I can see that page and it’s very helpful. Even more helpful would be a view of the “bug base” so I would know what’s being worked on/prioritized - I know you get to see that as as subscriber, not quite sure why non-subs can’t see it, but that’s their call. [import]uid: 39515 topic_id: 6352 reply_id: 25549[/import]

Hmm thats odd, I thought everyone could sign up for the bug base. Maybe its to stop newbees filling it with bugs that aren’t really bugs!

Anyway its not _that_ useful. A lot of the bugs i’m interested in don’t seem to be there. I think a lot are marked as private.

One major one right now is VERY slow laggy performance on motorola Droid phones and Nexus S on the daily’s. I’m going to keep harping on about it until its fixed :stuck_out_tongue:

The last stable has a bug with setidletimer so I cant keep the screen awake. Without the screen awake I need to implement suspend/resume (which i have already), but I cant use that because there’s no way to exit without the back button lol! [import]uid: 8872 topic_id: 6352 reply_id: 25552[/import]

Ah, although it SAYS only subscribers can sign up, turns out non-subs can, too. That’s what I get for believing what I read!

This *is* a huge project, so it’s not too surprising that any given bug/enhancement isn’t at the top. I imagine they have way more to do than they can very quickly.

I would very much like to see UI widgets (native or not) like checkboxes, radio buttons etc., along with full Android hardware interaction and control. Not to mention actual bug fixes.

Fortunately games can re-invent/re-design the UI at will and the users will accept that - guess I’ll focus on games for a bit, but I would really like to be able to offer full business-class development to clients. [import]uid: 39515 topic_id: 6352 reply_id: 25567[/import]

This issue is HUGE.

It confuses new developers like me that assumes the hardware button events can be handled. So I spend time looking for a solution that doesn’t exists yet. [import]uid: 31571 topic_id: 6352 reply_id: 32467[/import]

Hey Ansca Mobile, how about this issue. Hard BACK and MENU button are very important for us.

Read this: http://developer.anscamobile.com/forum/2011/02/10/control-back-menu-and-home-button


Thanks for your input. This is currently filed as case #744 in our internal bug base.

Tim

And read this too:
This is a huge usability issue. I did some user testing with a player…and this person naturally thought that the back button would take them to the previous screen. Having it exit confused them.
[import]uid: 9190 topic_id: 6352 reply_id: 39399[/import]

Don’t let this get buried.

Any Corona app that utilizes more than a single screen automatically becomes annoying to use because it exits instead of going back when the Back button is pressed. It’s like using a web browser that treated a click on the Back button as a Close Tab command. :frowning: [import]uid: 41955 topic_id: 6352 reply_id: 41552[/import]

Is there any forecast how fast this issue is getting solved? [import]uid: 7190 topic_id: 6352 reply_id: 42246[/import]

Android users always use BACK button to return to the previous state. If we cannot handle BACK button, when we press BACK, it will jump to previous application that opened.

Please focus on this issue. This is a big issue for android users.

PS. Sorry for my English. [import]uid: 30117 topic_id: 6352 reply_id: 42348[/import]

The same topic here:
http://developer.anscamobile.com/forum/2011/06/18/urgent-we-need-handle-press-event-back-and-menu-hard-button-android-phone#comment-42349
[import]uid: 9190 topic_id: 6352 reply_id: 42350[/import]

Yes, Ansca Mobile really needs to correct this. The search function isn’t a big deal, neither is the home…but the bigges issue is the back and menu button.

Ansca Mobile…ADD SUPPORT! [import]uid: 29181 topic_id: 6352 reply_id: 42579[/import]

+1 with this… confused when I first hit back button and it exited program.

This is required for android builds, kinda makes it pointless for android without it as EVERY user, uses it. [import]uid: 72726 topic_id: 6352 reply_id: 43242[/import]

+1 [import]uid: 13895 topic_id: 6352 reply_id: 43506[/import]

+1
I can’t produce any serious Apps until this bug gets solved :frowning: [import]uid: 7190 topic_id: 6352 reply_id: 44767[/import]

+1
Seriously, I wouldn’t publish my game for Android until this gets fixed. This should be the top priority bug for the Android version. [import]uid: 48095 topic_id: 6352 reply_id: 48666[/import]