Dianne, thanks for the reply. Do you mean that I better not to hide these buttons and let them always visible? Also, do you mean that I could port these buttons only on system bar (ex: the status bar) instead of reserving a screen region to implement them? As I know people choose one way to port these buttons on the status bar. But if possible, could you give me any comment about my original idea (even it is not feasible)? Or I can do it only on the system bar? Is it possible to add another bar for these buttons? If yes, where is the source code located for me to refer to?
Thanks for your time. On 3月10日, 下午4時07分, Dianne Hackborn <[email protected]> wrote: > You will need to reserve a part of the screen that is only for those buttons > and always visible. If they can be hidden, navigation in the Android UI is > broken. See the Android 3.0 system bar as an example of how this should > work. > > > > On Wed, Mar 9, 2011 at 7:13 PM, bryan <[email protected]> wrote: > > Hi All, > > > My Android platform does not have any physical button except the power > > key. > > I meet a problem on porting the Home / Menu / Back button on > > touchscreen. > > > I already searched the keyword to sdudy this issue in this group and > > found a > > similar discussion: > > >http://groups.google.com/group/android-porting/browse_thread/thread/7... > > > May I ask it again if there is anyway to achive the goal? Or it can be > > done only > > adding these buttons on status bar? > > > My orignial idea is to add an AppWidget on homescreen and implement > > these buttons. > > However, I met some problem at Home button porting (function doesn't > > work, terminate unusually). > > For Menu and Back Key, I don't have any idea to implement them. > > Do you have any insight about it? > > Even though I can finish the above efforts, how can I control these > > buttons to > > let them always display at partial region on screen? > > > One more thing is sometimes I have to hide these buttons for other > > purpose. > > I think I have overcome this part by using API setViewVisibility(xxx, > > View.INVISIBLE). > > > Any advice or information is great. Firstly I better to know if my > > idea can work. > > > -- > > unsubscribe: [email protected] > > website:http://groups.google.com/group/android-porting > > -- > Dianne Hackborn > Android framework engineer > [email protected] > > Note: please don't send private questions to me, as I don't have time to > provide private support, and so won't reply to such e-mails. All such > questions should be posted on public forums, where I and others can see and > answer them. -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
