(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. Why XML to define layouts/components?

My original first post doesn't seem to get approved, so let me try
again. :)

I'm wondering whether other Android newbies than me find the empathy
on XML layout troublesome? I realize we should strive to separate view
from logic and that XML is hip and trendy, but is it really necessary
for these relatively simple Android applications?

XML layouts involves more files and what feels like a lot of
"magic" (type unsafe) properties, and makes samples harder to follow/
type. It also can't be especially efficient to use findViewById
(whether BFS or DFS based) constantly?

It sort of reminds me of the differences between JSF and Wicket, where
the former was designed by people sitting in an ivory tower while the
latter was designed for and by people at the ground, comfortable with
Java. Which also leads me to wonder how come Android uses the old type-
unsafe int enum pattern and also, why fluent-interfaces/method-
chaining isn't used in greater extend?

/Casper

PS: You might want to fix the URL's to the group charter and FAQ as
they currently go into 404.

--~--~---------~--~----~------------~-------~--~----~

2. Widgets: Imageview doesn't support transparency/alpha

When the layout editor shows something different from the device,
always trust the device.

While the layout editor runs a part of the Android framework, it uses
java2D to do the final drawing instead of the Android drawing library
(because a lot of it is in native).

The porting of the Android drawing framework on top of Java2D is not
100% finish, so there are some discrepancies

Xav






-- 
Xavier Ducrohet
Android Developer Tools Engineer
Google Inc.

--~--~---------~--~----~------------~-------~--~----~

3. Debugger doesn't work

4. Widgets: Imageview doesn't support transparency/alpha

5. GLSufaceView rotation performance

6. VerifyError while trying to run Unit tests

7. ProgressBar doesn't allow control of visibility in AppWidgetProvider App Widget?