TrianguloY

now browsing by tag

 
 

When you press the search button in the app drawer, the keyboard is shown automatically.

When you press the search button in the app drawer, the keyboard is shown automatically.

However, if you use the search-app action (shortcut) from an item/gesture/whatever it is not shown and you need to press the search bar.

Is this the normal behaviour?

NOTE 1: pressing the search bar and then clicking BACK close the search drawer, but not the keyboard.

NOTE 2: from old post in this community, I think that some of you don’t have this problem, am I wrong?

]]>

I discover that, in latest beta, you added(or it was added) the feature to swipe from the ‘three points menu’ in the…

I discover that, in latest beta, you added(or it was added) the feature to swipe from the ‘three points menu’ in the app drawer, a Holo new feature only available in latest android versions.

With this, I though about a possible new feature, one of the Holo ones. To add in setting a ‘three points menu’ with ‘help’ to go to your page (depending on where settings you pressed it). The long press feature will stay as now.

I’m suggesting this to be more ‘Holo’ only. (Personally I never use that menu in android settings, but some users like it)

]]>

New suggestion (I think nobody suggested this before, but I can be wrong)

New suggestion (I think nobody suggested this before, but I can be wrong)

First: is it possible to the items to know when the screen is scrolling and when not?

If the answer is yes: what about a setting to ‘only show item when scrolling’? This way we could create marks to show in which screen we are, rectangles around the screens, etc, that are shown only when scrolling. (I know that in almost all cases the item will be a ‘do nothing’ shortcut)

]]>

About the duplication app bug in the app drawer: this morning I updated Airdroid.

About the duplication app bug in the app drawer: this morning I updated Airdroid. Now it’s duplicated, the old icon don’t work.

Someone else?

]]>

I realized…why is not an option in LLX to kill all? (The same as go app by app in running apps killing them)

I realized…why is not an option in LLX to kill all? (The same as go app by app in running apps killing them)

]]>

Pierre Hébert if you are going to rework the geometry menu, I have some suggestions, mainly add sub-settings in that…

Pierre Hébert if you are going to rework the geometry menu, I have some suggestions, mainly add sub-settings in that menu (the same as the different geometry settings but as a general floating menu) for example:

-one will be the actual geometry settings

-another one could be the possible new window resize tool

-add the front/back little menu

-a menu with some toggles (honour pinned items on/off, show/hide invisible items, enable/disable the drop feature…) and maybe functions as reset geometry

Take this as an idea. I’m sure it will give you others.

]]>

About adding items into folders/panels when waiting above them.

About adding items into folders/panels when waiting above them.

I know this was discussed before, and you add a delay to help, but now with a lot of panels…I really need an option to disable that feature (so you can’t add items into panels/folders dropping them).

Someone else? Maybe it’s only me.

]]>

[ 5] copy style from folder icon to folder icon, copies also background image of the folder (was this discussed…

[ 5] copy style from folder icon to folder icon, copies also background image of the folder (was this discussed before? Sorry if it was)

]]>

[ 4] When you have a long list in the app drawer, and you create a folder, the drawer automatically scroll to the…

[ 4] When you have a long list in the app drawer, and you create a folder, the drawer automatically scroll to the bottom…but one row above the folder itself

]]>

[ 3] In the recent apps of the app drawer in LLX, the first app that appear always (if you didn’t hide it) is…app…

[ 3] In the recent apps of the app drawer in LLX, the first app that appear always (if you didn’t hide it) is…app drawer! Of course it’s obvious, but I think it don’t need to be there 😉

]]>