I love the flexibility of LL…second to none.
When selecting an app, there is a brief delay before the app launches. In this time I usually see the selection effect rendered (holo versus plain). In Action Launcher, for example, as soon as I touch an item it is launched (no detectable delay). I find it most noticeable when bringing up the app drawer in the two launchers. I tried to set the tap event to launch the item, hoping to avoid the selection effect, but I’m not sure it has made a difference.
Is there something causing the delay? Should thr selection effect be optional? Is it something to do with waiting for a long tap to see about editing mode? It makes me think of programs that wouldn’t react until the mouse click up event instead of acting on mouse click down.
If it can be fixed by setting the tap to launch the item (as under event/gesture), maybe there could be a global setting to enable each item to launch its respective item on initial tap down event?
]]>
D5 Creation
< ![CDATA[
For the impatient under us – Fast launching: Set the following script in the touch event. (Note that this prevents any other action on the item)(the delay that might remain is the time the app actually needs to launch)
]]>
< ![CDATA[
if(event.getAction()==MotionEvent.ACTION_DOWN){
LL.startActivity(item.getIntent());
LL.getContext().overridePendingTransition(0,0);
}
]]>
< ![CDATA[
Wow, that was quick! (Both your response and the script) That seems to be just what I was looking for. Thanks!
Yeah, I realize I can’t long tap on anything that uses that script. Is there a way to automate turning on that script for all the items of the current desktop or panel/folder. I really don’t know my way around scripting, but I’m guessing a script that would be run on a folder or desktop that adjusts the default item touch event to use the script above?
]]>
< ![CDATA[
Just go to edit mode, make sure that no item is selected and then edit the event. It gets automatically applied to all items which don’t have already an action specified for this event.
I already knew what to do, so it wasn’t that hard to write & test a 3-liner 🙂
]]>
< ![CDATA[
Just a minor improvement, instead of:
LL.startActivity(item.getIntent());
Use:
item.launch()
This way it works for folder too and takes care of settings a few flags.
]]>
< ![CDATA[
Pierre Hébert that’s exactly why I didn’t use that. The launch method is visibly slower than the startactivity one, but for general purpose this is good I guess.
]]>
< ![CDATA[
Hum, that’s weird. Even if you keep the overridePendingTransition call?
If so then I guess some flag is causing the delay because actually the launch method is pretty basic.
]]>
< ![CDATA[
Pierre Hébert It might also just be Android intent oddity…
]]>
< ![CDATA[
Maybe, especially since Lightning use some rarely used flags. Border effects can be seen, such as weird animation when coming back to the launcher after picking an image.
]]>