Thank you very much, Mark. You are right if I have a business goal, I should try to reach it with whatever means. However, currently my given task is to detect HOME screen. What is after that? I don't really know: MAYBE to start another application or MAYBE something else. :-)
Is "detecting HOME screen" a mission impossible? I would like to know too. Cheers, Sherry On Jun 5, 11:09 am, Mark Murphy <[email protected]> wrote: > sherry wrote: > > Thanks again. I'm confused. How can lower the thread priority can let > > me know if the screen is at HOME? > > Stop focusing on one technical solution (finding out when the device is > on the home screen) and focus on the business objective: you want to > minimize interference between your application and other running > applications. > > Lowering your thread priority is one way to achieve that business > objective, without having to worry about what exactly is running. In > particular, it will not matter whether the home screen is active or not. > > After all, not everybody returns to the home screen and leaves their > phone in that state, so your intended solution (do work when the device > is on the home screen) will not work for a significant number of users. > > -- > Mark Murphy (a Commons > Guy)http://commonsware.com|http://twitter.com/commonsguy > > Warescription: Three Android Books, Plus Updates, $35/Year --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Beginners" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en -~----------~----~----~----~------~----~------~--~---
