(Bug?) Back button triggers several times in different tasks

by 椤惧仴 » Thu, 13 May 2010 01:22:43 GMT


Sponsored Links
 Android v1.6 hasn't the method of onKeyDown() and onBackPressed() .Can I use
another method to replace them?

2010/5/12 Mark Murphy <mmur...@commonsware.com>

>



(Bug?) Back button triggers several times in different tasks

by Mark Murphy » Thu, 13 May 2010 01:24:49 GMT


 


onKeyDown() has existed for over two years, the same length of time as
the onKeyUp() that your re presently using. onKeyDown() exists in
Android 1.6.

-- 
Mark Murphy (a Commons Guy)
 http://commonsware.com  |  http://github.com/commonsguy 
 http://commonsware.com/blog  |  http://twitter.com/commonsguy 

Android 2.x Programming Books:  http://commonsware.com/books 

--


Sponsored Links


(Bug?) Back button triggers several times in different tasks

by gujian » Thu, 13 May 2010 21:43:33 GMT


 I think this situation depend on A'status.you can debug it with "Log.d()"and
then you can get your answer!

2010/5/13 inbrain <inbr...@gmail.com>




> >



(Bug?) Back button triggers several times in different tasks

by gujian » Fri, 14 May 2010 09:16:14 GMT


 we can get some message from your strange result.when you pressed back
button the A's onkeyup() was triggered.that is A shoud be activity.of
course  contents of above is my assumption which need your debug.in fact ,I
am new to android and unfamiliar with the method of intent.setComponent.I'm
sorry for that.

2010/5/13 inbrain <inbr...@gmail.com>





> > > >



Other Threads

1. How to call a view from the view ?

Hi guys.

I am a new developer for Android. I wanna know about View transitions.

For my application, it has 5 screens that can shift each other.

In order word, Screen1 -> Screen2 <--> Screen3 <--> Screen4 ->
Screen5.

How to make this screen transition on Android ?

Please share the knowledge.

Thanks in advance.

-- 

2. Where can I catch a point that is assured to be called when a Service is destroied

> I have a Service, it is started by StartService(...), my program never

There is no "right point" for those scenarios. Your code will not be
called. Hence, do not wait to be destroyed to "clean up and save
settings".

And, please do not leave your service running all of the time:

http://www.androidguys.com/2009/09/09/diamonds-are-forever-services-are-not/

-- 
Mark Murphy (a Commons Guy)
http://commonsware.com
Android App Developer Books: http://commonsware.com/books.html


-- 

3. How to keep mobile network alive even if screen is off

4. Busy Coders Guide is 拢204/$24 0 on Amazon...

5. <WTA> force close dream...

6. Replacing existing TabHost content

7. request queue pointer null in add_disk