Can you guys point me to some best practices on maintain options menus
in Android applications.  I understand the concept that the options
menu is meant to be for a particular activity, but it has to be fairly
common that multiple activities share very similar menus.  So, is
there some one to have an application wide menu and call that after
creating an options menu for an activity. Along the lines of calling
the super class.  Do I somehow subclass the options menu for my app,
call my create which first call this sub class and then populates the
activity specific stuff?  Is this the right pattern?  Do y'all know of
examples specific to Android?  I appreciate any assistance you can
provide.

Mark

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" 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-developers?hl=en

Reply via email to