Nexus 7 has no menu button? - Android Developers

The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Message from discussion Nexus 7 has no menu button?
Date: Sat, 29 Sep 2012 12:54:48 -0700 (PDT)
From: Rudolf Hornig <rudolf.hor...@gmail.com>
To: android-developers@googlegroups.com
Message-Id: <1e9dfc3f-d8ea-43bb-9049-f219469f6d99@googlegroups.com>
In-Reply-To: <b57e064e-84b4-4b3c-b3f5-40055738bfe9@googlegroups.com>
References: <b57e064e-84b4-4b3c-b3f5-40055738bfe9@googlegroups.com>
Subject: Re: Nexus 7 has no menu button?
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_482_24824349.1348948488441"

------=_Part_482_24824349.1348948488441
Content-Type: multipart/alternative; 
	boundary="----=_Part_483_7031076.1348948488441"

------=_Part_483_7031076.1348948488441
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Hi all, I just run into this issue too.

I'm using minsdk set to 8 and target to 11. According to the blog here:
http://android-developers.blogspot.hu/2012/01/say-goodbye-to-menu-button.html


   - 
   
   If you set either minSdkVersion or targetSdkVersion to 11 or higher, the 
   system *will not* add the legacy overflow button.
   - 
   
   Otherwise, the system *will* add the legacy overflow button when running 
   on Android 3.0 or higher.
   - 
   
   The only exception is that if you set minSdkVersion to 10 or lower, set 
   targetSdkVersion to 11, 12, or 13, and you do not use ActionBar<http://developer.android.com/reference/android/app/ActionBar.html>, 
   the system *will* add the legacy overflow button when running your app *on 
   a handset* with Android 4.0 or higher.
   

This would indicate that I meet the third (exception) condition so it would 
have a compatibility action overflow button, and indeed, it appears on my 
Galaxy Nexus running jelly bean, but NOT on a Nexus 7.
i.e. The Nexus 7 and the Galaxy Nexus behaves differently even if they are 
running the same OS version...

Is this because the Nexus 7 is not considered a *handset* ???

I feel this was not a good decision to have different behavior for 
different form factors that FUNCTIONALLY handicap the programs.
Does anybody have information on this?

Rudolf

On Wednesday, September 19, 2012 10:42:44 PM UTC+2, Keith Wiley wrote:
>
> I don't have access to a Nexus 7 but I'm getting feedback from users that 
> they can't access the menus in my app...like, at all...which I find 
> perplexing since I use the same standard menus that all Android apps use 
> (including the Android home-screen).  If the Nexus 7 doesn't have a 
> relatively obvious menu button, it seems to me that the majority of Android 
> apps, including the home-screen, would be veritably unusable.
>
> Can anyone help me understand what's going on here?
>
> Thanks.
>
>
------=_Part_483_7031076.1348948488441
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi all, I just run into this issue too.<div><br></div><div>I'm using minsdk=
 set to 8 and target to 11. According to the blog here:</div><div><a href=
=3D"http://android-developers.blogspot.hu/2012/01/say-goodbye-to-menu-butto=
n.html">http://android-developers.blogspot.hu/2012/01/say-goodbye-to-menu-b=
utton.html</a><br></div><div><br></div><div><ul style=3D"padding: 0px 2.5em=
; margin: 0.5em 0px; line-height: 12px; color: rgb(51, 51, 51); font-family=
: 'Droid Sans'; background-color: rgb(249, 249, 249); "><li style=3D"paddin=
g: 0px; margin: 0px 0px 0.25em; "><p>If you set either&nbsp;<code>minSdkVer=
sion</code>&nbsp;or&nbsp;<code>targetSdkVersion</code>&nbsp;to 11 or higher=
, the system&nbsp;<em>will not</em>&nbsp;add the legacy overflow button.</p=
></li><li style=3D"padding: 0px; margin: 0px 0px 0.25em; "><p>Otherwise, th=
e system&nbsp;<em>will</em>&nbsp;add the legacy overflow button when runnin=
g on Android 3.0 or higher.</p></li><li style=3D"padding: 0px; margin: 0px =
0px 0.25em; "><p>The only exception is that if you set&nbsp;<code>minSdkVer=
sion</code>&nbsp;to 10 or lower, set&nbsp;<code>targetSdkVersion</code>&nbs=
p;to 11, 12, or 13, and you do not use&nbsp;<a href=3D"http://developer.and=
roid.com/reference/android/app/ActionBar.html" style=3D"color: rgb(37, 138,=
 175); ">ActionBar</a>, the system&nbsp;<em>will</em>&nbsp;add the legacy o=
verflow button when running your app&nbsp;<em>on a handset</em>&nbsp;with A=
ndroid 4.0 or higher.</p></li></ul><br>This would indicate that I meet the =
third (exception) condition so it would have a compatibility action overflo=
w button, and indeed, it appears on my Galaxy Nexus running jelly bean, but=
 NOT on a Nexus 7.</div><div>i.e. The Nexus 7 and the Galaxy Nexus behaves =
differently even if they are running the same OS version...</div><div><br><=
/div><div>Is this because the Nexus 7 is not considered a *handset* ???</di=
v><div><br></div><div>I feel this was not a good decision to have different=
 behavior for different form factors that FUNCTIONALLY handicap the program=
s.</div><div>Does anybody have information on this?</div><div><br></div><di=
v>Rudolf</div><div><br></div><div>On Wednesday, September 19, 2012 10:42:44=
 PM UTC+2, Keith Wiley wrote:<blockquote class=3D"gmail_quote" style=3D"mar=
gin: 0;margin-left: 0.8ex;border-left: 1px #ccc solid;padding-left: 1ex;">I=
 don't have access to a Nexus 7 but I'm getting feedback from users that th=
ey can't access the menus in my app...like, at all...which I find perplexin=
g since I use the same standard menus that all Android apps use (including =
the Android home-screen).&nbsp; If the Nexus 7 doesn't have a relatively ob=
vious menu button, it seems to me that the majority of Android apps, includ=
ing the home-screen, would be veritably unusable.<br><br>Can anyone help me=
 understand what's going on here?<br><br>Thanks.<br><br></blockquote></div>
------=_Part_483_7031076.1348948488441--

------=_Part_482_24824349.1348948488441--
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
Account Options
