A suggestion for consistency.
(Every time I say ‘menu’ I’m referring to the lighting pop-up menu, by default on long click)
Edit: this menu have other entries too (add item, edit layout…) I’m only writing the ones referring to ‘settings’
Now:
When you open the menu from the desktop you have
-Android settings
-Lighting settings
—All settings
—Current desktop
—Lock
When you open the menu from a panel you have
-Android settings
-Panel settings
-All settings
When you open the menu from a folder you have
-Android settings
-Folder settings
My suggestion:
When you open the menu from the desktop you will have
-Settings…
—Lightning Launcher
—Current desktop
—Android
-Lock
When you open the menu from a panel you will have
-Settings…
—Lightning Launcher
—Current panel
—Android
When you open the menu from a folder you will have
-Settings…
—Lightning Launcher
—Current folder
—Android
]]>
< ![CDATA[
I must not be understaning what you mean by menu, in a long press on the desktop, the menu that pops up is a 6 item list that’s identical to the menu that pops up when I long press in a folder except instead of “Lightning Settings” “Folder Settings” appears.
]]>
< ![CDATA[
That’s what I mean, I didn’t wrote all the items of the menu, only the necessary ones.
The list is identical, but folder settings opens the folder settings, and lighting settings opens another menu with 3 items.
That’s what is a bit inconsistent to me
]]>
< ![CDATA[
I understand what you mean, but I am confused about grouping: did you put some indentation that does not appear in the post ?
As I understand items for the desktop would be:
1) Settings…
1.1) Lightning Launcher
1.2) Current Desktop
1.3) Android
2) Lock
Is this right ?
The Android settings was initially in the first level for fast access but indeed, it may not be that useful.
The lock menu item could be added to panels and folders too.
]]>
< ![CDATA[
It is right.
I placed the lock item out because it is not related to settings.
]]>
< ![CDATA[
Eh! It was true, on the web version of google+ indentation is not shown, but on the android app it is (for me)
I changed the post with lines
]]>
< ![CDATA[
Maybe this is due to html squeezing multiple occurences of white characters!
]]>