EDIT: this function must be called with false for the value param.
On Monday, 21 October 2013 10:14:14 UTC+2, b0b wrote:
>
> You can force the appearance of the Overflow menu when a physical menu key
> is present with this hack below, calling that function with true for value.
>
>
--
You receiv
You can force the appearance of the Overflow menu when a physical menu key
is present with this hack below, calling that function with true for value.
Not sure it still works on rcent versions of Android though. And of couse,
someone is probably going to say "don't do it!".
static public voi
This snippet of Android Source Code leaves me more confused than ever about
what the HasPermanentMenu() function does.
If it doesn't have a SystemNavbar and it doesn't have a NavigationBar(), it
must have a permanent menu button? Huh?
From
http://grepcode.com/file/repository.grepcode.com/java
I strongly disliked the way the Menu button was treated, too. For a while
I tried to figure out a rule like the one you mention to allow me to use
the button at least where it's available but after several failures we
decided we couldn't afford using our users to test on the vast array of
Android
I have found this function in my research.
ViewConfiguration.get(context).hasPermanentMenuKey()
One would assume then that
API<11 => implies menu button is available.
API of 11-13
However, should I take the name too literally? Would a menu soft key that
appears only in portrait be conside
My third paragraph should read:
Forcing an overflow button, which I think should be a standard Android
style, was once supported by ActionBarSherlock for 2X devices and is now no
longer available. It never worked for 4.X devices where manufacturers
insist on having that menu button.
--
You r
6 matches
Mail list logo