Cool, thanks. I'll give that a try and report my findings back here.
String
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email
Whether or not the menu button is shown is purely based on the
targetSdkVersion of the app.
On Wed, May 18, 2011 at 6:07 PM, String wrote:
> Yeah, my API level's already set to 12 here, that's why my menu button's
> gone away (as you say). I'm finally on the trail of bringing apps up past 10
> no
Yeah, my API level's already set to 12 here, that's why my menu button's
gone away (as you say). I'm finally on the trail of bringing apps up past 10
now that I have this great HC tablet somebody gave me in SF.
But would it be possible, then, to drop my target back down to 10, inherit
my themes
Yeah it works down to 4.
My response about the API level was strange, I missed that the issue the
original poster had is that for API 11 apps there is no menu button
available.
On Wed, May 18, 2011 at 3:01 PM, Zsolt Vasvari wrote:
> Thanks, Dianne. I thought there might be a better way. Does
Thanks, Dianne. I thought there might be a better way. Does this
work down to API level 4?
I am not sure I understand the point of your comment about the
targetSdkVersion. Of course, I have it defined as 11 (actually 12).
Otherwise I wouldn't need to mess around with the Holo stuff. Maybe I
am
You actually don't need to do something that complicated. You can just
define your own custom theme that switches based on the API version... hm
I thought this was documented, but maybe I saw it in some newer in-progress
documentation. Anyway, just define a theme that inherits from the pre-v11
Yeah, I don't dispute that.
The functionality on the menu is rarely used, not critical, and I wouldn't
be surprised if no real-world user even knows it's there. Longer-term, my
plan is to incorporate this dialog into the parent activity on xlarge
screens... but until then, I'm probably OK to ju
Hey, that's pretty slick. I hadn't thought of using static inner
Activity classes to address this problem. Thanks!
On Wed, May 18, 2011 at 8:21 AM, Zsolt Vasvari wrote:
>> 1. On API Level 11+, use a version of the activity that isn't themed
>> as a dialog. I hoped you could use for this, but it
> 1. On API Level 11+, use a version of the activity that isn't themed
> as a dialog. I hoped you could use for this, but it
> doesn't seem like you can override a theme that way...
What I do is the following:
public class MyActivity extends Activity
{
public static class MyActivityNoHolo e
What you are doing is highly unusual. I would say no user would
anticipate that there would be a menu on a dialog. It's possible that
the designers of Honeycomb weren't even thinking of the possibility of
this.
On May 18, 8:08 pm, String wrote:
> I have an Activity which appears like a dialog (
10 matches
Mail list logo
