1. Currently we have “auto close” for folders; it will close the folder when an app from it is launched. I’d like to close a folder when another folder is opened (from the desktop or panel or folder).
I’d like to have 2 open folders but not 3.
I want to use folders because I can’t hide panels.
Is there any other way of doing it?
2. Is there a way to disable gestures on a desktop? I have a desktop locked in portrait and one that can be both portrait and landscape and I don’t want my folder gesture to work in landscape.
More details, there will be preliminary support for hiding/showing items soon. Also scripting will enable fine management of which folders are open or not. Regarding gestures I am currently looking at a way to handle them per desktop, but even if it is not available through configuration menus, scripting will enable this too.
Pierre Hébert I’m not sure what you mean by a “brick” (overkill maybe). It’ll be awesome functionality to look forward to once you’ve had time to think it all through.
As always thank you so much for an already quite brilliant launcher 🙂
Yes exactly, like the brick in the wall. Maybe the word is not well chosen (direct translation from what I would have said in French…). Another way to explain is a piece in the puzzle. One piece is edition and management of scripts. One is actually executing scripts, another one is binding launcher capabilities into the script executor so that scripts can do valuable things, and another one is bring more data into the loop, for instance using tasker variables. There are other smaller pieces in the puzzle, but I hope biggest holes will be filled one day 😉
D5 Creation
< ![CDATA[
1. soon !
2. soon !
More details, there will be preliminary support for hiding/showing items soon. Also scripting will enable fine management of which folders are open or not. Regarding gestures I am currently looking at a way to handle them per desktop, but even if it is not available through configuration menus, scripting will enable this too.
]]>
< ![CDATA[
Pierre Hébert when you say “scripting” might that mean something along the lines of Tasker integration? 🙂
]]>
< ![CDATA[
Tasker integration will be a brick in scripting. It may not be in the first alpha/beta versions, but I hope it will be there in the stable release.
]]>
< ![CDATA[
Pierre Hébert I’m not sure what you mean by a “brick” (overkill maybe). It’ll be awesome functionality to look forward to once you’ve had time to think it all through.
As always thank you so much for an already quite brilliant launcher 🙂
]]>
< ![CDATA[
Brick = part of the wall.
]]>
< ![CDATA[
Yes exactly, like the brick in the wall. Maybe the word is not well chosen (direct translation from what I would have said in French…). Another way to explain is a piece in the puzzle. One piece is edition and management of scripts. One is actually executing scripts, another one is binding launcher capabilities into the script executor so that scripts can do valuable things, and another one is bring more data into the loop, for instance using tasker variables. There are other smaller pieces in the puzzle, but I hope biggest holes will be filled one day 😉
]]>