@TreKing
Yet another of my typos! I meant Mark M., not Bob M.
On Jun 8, 2:26 pm, TreKing treking...@gmail.com wrote:
On Wed, Jun 8, 2011 at 4:14 PM, Indicator Veritatis mej1...@yahoo.comwrote:
But you are wrong to deny the causal link between pressing Home and the
lifecycle in turn causing
But as Mark Murphy already pointed out in this thread, Do not request
the HOME category unless *you
are a home screen*.
Mark Murphy is not only an outstanding Android programmer, one with
experience from very early in Android's short history, but one of the
star contributors to this forum, as
activity android:name=.OnHome
android:label=OnHome
intent-filter
action android:name=android.intent.action.MAIN /
category android:name=android.intent.category.HOME /
category android:name=android.intent.category.DEFAULT /
/intent-filter
I think you need a holiday.
On Jun 8, 1:13 pm, Mark Murphy mmur...@commonsware.com wrote:
On Wed, Jun 8, 2011 at 7:20 AM, Mark Murphy mmur...@commonsware.com wrote:
On Wed, Jun 8, 2011 at 2:31 AM,Droidrod...@gmail.com wrote:
I need to know when the home button is pressed too (otherwise my
On Fri, Jun 10, 2011 at 10:43 AM, Droid rod...@gmail.com wrote:
Above would be really cool if it worked, but it worked not.
Above would be a bug if it worked, because it's not supposed to work like
that.
Still cannot detect on home button click to turn off my timer thread.
Once again,
action android:name=android.intent.action.MAIN /
category android:name=android.intent.category.HOME /
category android:name=android.intent.category.DEFAULT /
Add this intent filter for the activity you want to invoke on the
press of home button.
On Jun 8, 1:05 pm, TreKing
I need to know when the home button is pressed too (otherwise my app
returns to visibility again and again for ever).
Is there a hack? (Please don't tell me I need to design my app
'properly', I have been Android dev for over a year now)
--
You received this message because you are subscribed to
On Wed, Jun 8, 2011 at 2:31 AM, Droid rod...@gmail.com wrote:
I need to know when the home button is pressed too (otherwise my app
returns to visibility again and again for ever).
Then fix your bug.
(Please don't tell me I need to design my app
'properly', I have been Android dev for over a
On Wed, Jun 8, 2011 at 7:20 AM, Mark Murphy mmur...@commonsware.com wrote:
On Wed, Jun 8, 2011 at 2:31 AM, Droid rod...@gmail.com wrote:
I need to know when the home button is pressed too (otherwise my app
returns to visibility again and again for ever).
Then fix your bug.
(Please don't
Sent from my Verizon Wireless Phone
-Original message-
From: Mark Murphy mmur...@commonsware.com
To: android-developers@googlegroups.com
Sent: Wed, Jun 8, 2011 08:21:34 GMT-03:00
Subject: Re: [android-developers] Re: In Android, how to get the keyevent of
'home Key' ?
On Wed, Jun
Your blog post IS the best explanation I have seen to date of what the
Home key really means. I thought it was particularly interesting that
it emphasized something I have been dimly aware of but keep
forgetting: unlike the Back key, pressing Home does NOT cause finish()
to be called. I assume
On Wed, Jun 8, 2011 at 12:31 PM, Indicator Veritatis mej1...@yahoo.comwrote:
But shouldn't it trigger onStop() too? After all, the application is
no longer visible. And what about the Activity Stack? Doesn't pressing
Home put the least recently used Activity on that stack?
Yes and yes
Think of home like alt-tab in windows. You never need to capture it.
You just need to handle onPause()/onStop() in a way that makes sense
for the user temporarily leaving your app. You'll get onFinish() when
your app is to be actually destroyed. If you have a need to actually
kill off the whole
Confusion easily comes from thinking about the home screen and the home key
as being more special than they are.
The home screen, to a large degree, is just another application. When it
comes to the foreground, the usual rules with onPause / onStop apply to the
current application.
As for not
You guessed correctly. Where I wrote 'least', I should have written
'last'. But since you agree that both onPause() and onStop() will be
called, Bob M. really has to change the wording in his blog. As it
stood when I wrote that, it really did imply that ONLY onPause() is
called, not onStop(). As
On Wed, Jun 8, 2011 at 4:14 PM, Indicator Veritatis mej1...@yahoo.comwrote:
But you are wrong to deny the causal link between pressing Home and the
lifecycle in turn causing onPause() and onStop() to be called. It is not
only perfectly correct, but even important to understand the lifecycle as
I don't remember anyone asking
how to prevent the user from pressing the power key to unlock the phone :)
That's be because the power key doesn't unlock the phone :P, it wakes
it up, then you slide to unlock.
I do actually get user requests to disable the power key from waking
the device, but
17 matches
Mail list logo
