V14.1b1 beta
A quick update to let you know that a new 14.1b1 beta version is coming.
It contains a few new features related to events and actions. In short it is now possible to configure several actions for a single event, without the need for a script.
While the feature is mostly complete, there are areas where the behavior need to be tuned. I am thinking at a particular case: when chaining actions like “go to previous desktop, then zoom full scale”, it won’t work as expected because all actions are currently started using the context found at the time of the event. Hence the zoom fullscale action will operate on the initial desktop, not the previous desktop. I am currently trying to improve this.
Other than that I hope it will work just fine and that it will help in setting up interesting things.
Full ChangeLog: http://www.lightninglauncher.com/wordpress/change-log/
]]>
D5 Creation
< ![CDATA[
awesome. thanks for always improving this already fantastic launcher!
]]>
< ![CDATA[
Cool update !
For the context behavior, maybe add a checkbox for some action that act upon a context, so we can choose if the action should use the origin context or not..
]]>
< ![CDATA[
Cool!
Just two little improvements:
1)When you long tap a shortcut in edit mode, there is a ‘select shortcut’ entry. When you click that it shows directly the list of shortcuts to choose (which is fine if the previous intent was a normal shortcut), but not if it was a list of shortcuts.
2) Now the list of lightning actions is sorted in categories (nice!). But the ‘lock do nothing’ is under advanced…and personally I think it should be the first option (maybe without a category, or inside a ‘default’ one). Not sure about ‘unset’.
]]>
< ![CDATA[
I prefer to keep things as simple as possible and avoid more checkboxes 🙂 What I am trying to do is explore as much situations as possible and compare the expected behavior with the current. I don’t think there are too many possibilities. Based on that, I’ll tune the event parameters so that it behaves naturally. In some cases it may not match user expectation, but it may be possible to fix this by reordering actions or… with a script ;-)
]]>
< ![CDATA[
Some of the combined options are pretty obsolete, e.g. Go home + zoom 100p
This could be solved with two actions
]]>
< ![CDATA[
If is user in screen add action and doing rotate your phone, this screen is closed now…
]]>
< ![CDATA[
In New screens for add action I have problem with translations… Because Czech words are longer than English. Can you please enable add second line for text?
https://lh3.googleusercontent.com/gW25cc4RqpxGu4rF7FBsqqYyUrDA_U-u3ZIjmssUzbrkKYrNJfxhItUvKaWaXf9yyJRqDQwkrGs
]]>
< ![CDATA[
https://lh3.googleusercontent.com/p0VetwpGX2-lhQYCxGCUvBjr_n6i0U8DEz4U_eOj1iTRKBaFZlRPo8QGnBNfA7j5eAzopkDF4cw
]]>
< ![CDATA[
https://lh3.googleusercontent.com/xgmp-KUwwp8JWM5xqGXm2cX3A0THTPnaVkkH5irwLrVZ0V9IIlvD67tkRXc4Vz_5FS6ACM4IIwM
]]>
< ![CDATA[
When user add new second actions, they must tap to done button, because if doing tap to back key, second action will be remove.
]]>
< ![CDATA[
I’ve found strange thing.. and it happens from earlier versions:
If I swipe pages of my desktop and touch the screen before page stops the page stops between pages.. is it normal?
]]>
< ![CDATA[
Lukas Morawietz not this one, because there’s a condition between, the second will only be executed if the first is a no op.
Danbar Danbar thanks, I’ll take this into account. The back key purpose is to cancel, but I could as well add a cancel button and prevent the back key to leave the screen or make it save changes.
Станислав Владимирович this is normal, this is the same behavior as when you scroll a list, touching the screen stops the scrolling, otherwise you won’t be able to start a new fling as long as the current scroll is not finished.
]]>
< ![CDATA[
Pierre Hébert (just in case you missed it, I posted a comment here. Third from above)
]]>
< ![CDATA[
TrianguloY yes I missed it, thanks!
]]>
< ![CDATA[
TrianguloY finally I merged the “Select app” and “Select shortcut” menus in a single “Edit launch action” which will do the appropriate job according to the underlying action type, that’s way more consistent this way. I also removed Unset because this action (or more precisely “lack of action”) is filtered anyway. I first thought that moving “Do nothing” at the top without a category would look a bit weird, but after all it isn’t so bad, so I’ll leave it this way.
]]>