V14a1 alpha
Edit: V14a2 to fix some urgent bugs and crashes.
Today I’m announcing the release of the first alpha for the upcoming V14 🙂
It consists in a huge architecture overhaul. The aim is to remove some longstanding limitations and bugs, improve efficiency in some areas and allow upcoming evolutions. It took me a lot of time to release it, but I think it works reasonably well now.
In spite of the massive amount of code changes, my aim is that V14 will remain as most compatible as possible with V12.
There are some differences though 😉 Please read http://www.lightninglauncher.com/wordpress/changes-beteen-v12-9-1-and-v14/ for the exact list.
One particular change is the ability to display the same content in multiple locations. To explain this, let’s imagine there’s a complex panel you would like to see on multiple desktops. With v12 you need to copy it. Subsequent changes to this panel on one desktop will have to be repeated on all desktops. With v14 it is possible to link the content. In other words, any change made to one version will be immediately available to all other versions.
There are more uses for this feature: the content of a folder can be displayed in a panel (and vice versa), the content of the app drawer can be displayed in a panel (that is: in a desktop), it is possible to quickly switch the content of a panel, and so on.
At the moment the feature can only be accessed through script (see Folder/Panel.setContainerId) but this API has no restriction, meaning that all kind of funny/weird/insane stuff is possible. Including recursion and the aforementioned app drawer in desktop… Please use with care… Ahem, no, don’t use with care, let’s play with it, it’s fun and as with all new strange feature, I’m eager to see what you can do with it!
As this is an alpha, please be aware that it may be unstable, corrupt your setup or crash. Make sure you have a backup and that you are able to restore the stable version if needed.
Opt-in link for the APK: https://play.google.com/apps/testing/net.pierrox.lightning_launcher_extreme
Enjoy!
]]>
D5 Creation
< ![CDATA[
you just skip the V13？
]]>
< ![CDATA[
Yes !
]]>
< ![CDATA[
nice!
]]>
< ![CDATA[
Someone said fun? 😀
]]>
< ![CDATA[
Youpieeeeeeeeeeee !
]]>
< ![CDATA[
Great News Pierre !
]]>
< ![CDATA[
https://lh3.googleusercontent.com/pvR3EbKGvxp8nERewaHKgJ96synpYRigH-Fr_lbVp1Ns7Cd-a8XKxyiRTypjnz_r4gBSegz4lw
]]>
< ![CDATA[
Woo hoo! What a surprise to wake up to!
]]>
< ![CDATA[
Amazing.
]]>
< ![CDATA[
13 is unlucky makes sense to skip it 😉
]]>
< ![CDATA[
Woooo!!
i can’t stop being my lips upwards :-}
]]>
< ![CDATA[
Could these changes make it possible to use support library’s through script? I mentioned before about scripting a toolbar.
]]>
< ![CDATA[
Great news! can’t wait to give it a try! but like shelter never my beta page also shows signup in progress.. even though I’m on beta since a few months.. Anyone else also experiencing the same?
]]>
< ![CDATA[
manish kumar same for me. 🙁
]]>
< ![CDATA[
It’ll come in eventually.
]]>
< ![CDATA[
The update should have appear already. Maybe you need to manually opt-out of the beta and opt-in again for the alpha.
Jay M no yet. Do you have a link to your post, I don’t recall about it, sorry 🙁
]]>
< ![CDATA[
Pierre Hébert tried opt out and opt in with no luck.
]]>
< ![CDATA[
Amit Patil I had the same. Opted out, opted in again and rebooted phone. After reboot I could download the V14 version
]]>
< ![CDATA[
Pierre Hébert here it is https://plus.google.com/113157980543803349502/posts/WLaE3DmdaWG
]]>
< ![CDATA[
OU YES!
]]>
< ![CDATA[
Looks nice. This might make me play with my set-up again
]]>
< ![CDATA[
didn’t have to do anything.. update came and the beta message shows fine now 👍 now on to testing 😊
]]>
< ![CDATA[
+Pierre Hébert I updated and now can’t do a thing! Nexus 5x 7.0 Sept update. Crashes immediately without putting anything except KLWP wallpaper.
]]>
< ![CDATA[
Pierre Hébert when I try to lunch any app from the drawer it hangs and shows no response dialog to kill the app.
One more thing? Can we change the homescreen in this version through a script although I would prefer to have an action in Tasker plugin.
]]>
< ![CDATA[
+Glenn Beard . Same thing here. I send a few bugreports 👍👍
]]>
< ![CDATA[
Sent some bug reports .
Except of that it works fine
]]>
< ![CDATA[
Any of you with crashes tried a reboot?
]]>
< ![CDATA[
Jay M I did
]]>
< ![CDATA[
Roger Schreuders Did same. Glad it not just me. Jay M Yes tried reboot no change.
]]>
< ![CDATA[
Jay M yes i did. I forgot to mention that i completely LL. I use v14a1 from scratch.
Well, it’s an alpha release… ☺
]]>
< ![CDATA[
Thanks for all the bug reports, I am processing them at the moment, it will take some time lol! I hope to push an update later today though.
Abdullah Alahdal Do you have scripts or bindings in the app drawer? The home screen can be changed using this new API: .http://www.lightninglauncher.com/scripting/reference/api-alpha/reference/net/pierrox/lightning_launcher/script/api/Configuration.html#setHomeDesktopId(int)
]]>
< ![CDATA[
An update is coming with several important bug fixes, some of them seen right at startup. Thanks for the flood of emails 🙂
]]>
< ![CDATA[
V14a2 works👍.
]]>
< ![CDATA[
Works but the issue with getID targeting only ID 0 is still here
]]>
< ![CDATA[
Yes, I am sorry I couldn’t find a fix yet
]]>
< ![CDATA[
No issue I managed to scroll most of my panel. My screen is a bit clustered but I can wait:)
]]>
< ![CDATA[
Pierre Hébert is there an issue with getItemById() or getItembyName() in the new scripting API? I use a binding which runs a script via runScript(“script”, item.getId()); . In script I try var it = getEvent().getScreen().getIemById(getEvent().getData()); . This causes an error that object has no method getItemById. The same error with deprecated LL.getItemById(getEvent().getData());.
]]>
< ![CDATA[
Bob Koomans Same here on my unrooted Note 4 with stock 6.0.1 MM
]]>
< ![CDATA[
Pierre Hébert after uninstalling I’m no more able to reinstall the new beta. No install button on beta link for me.
Edit : i’ve left testing prog + reinstalled last stable + reswitched to beta testing.. Now waiting for the update ☺
Edit2 : back in beta yeaaah
]]>
< ![CDATA[
Emmanuel LapierreI found the issue, the container is valid but the setPosition method is broken. I’ll publish an update tomorrow probably.
Mirko Kohler it seems that getScreen() returns null here. I’ll have a look at runScript triggered from a binding, the issue probably comes from here.
]]>
< ![CDATA[
Mirko KohlerI tried to reproduce this issue but it works for me. Just in case, you wrote “getIemById”, this is a typo in your post, not in your code ?
]]>
< ![CDATA[
Pierre Hébert it’s a typo.
Binding (dummy) code: runScript(getActiveScreen(),”MK dateView”,item.getId());
return $ll_minute;
Script code:
var ev = getEvent();
var it = null;
if(ev.getData() == null) it = ev.getItem();
else
it = getEventScreen().getItemById(ev.getData());
Error:
At line 5: TypeError: Cannot find function getItemById in object net.pierrox.lightning_launcher.script.api.b.c@bf8827c.
]]>
< ![CDATA[
Mirko Kohler the only way I see to get this message is to use a null argument, but this is checked just before, so I am lost. Could you please extract the code in a separate desktop and send it to me as an exported template?
]]>
< ![CDATA[
Pierre Hébert mail with exported template sent.
]]>
< ![CDATA[
Pierre Hébert
I used below code and could change the home screen however the goToDesktopPosition is giving me error. Do I have to call something before this command.
var c = getConfiguration();
c.setHomeDesktopId(1);
goToDesktopPosition(1,0,0);
One more thing, you are awesome.
]]>
< ![CDATA[
Abdullah Alahdal this would be something like getActiveScreen().goToDesktopPosition or getEvent().getScreen().goToDesktopPosition but I discovered that it is currently broken. You may have more luck with the older APIs (I didn’t tested them)
]]>
< ![CDATA[
Pierre Hébert thanks. As a workaround, I used TaskerIntent with Go_Home action.
]]>
< ![CDATA[
Mirko Kohler I found the issues. In fact there are two issues, one in your script, one in Lightning.
The first one is getActiveScreen() : use getEventScreen() instead. The first time bindings are evaluated, the screen is not yet displayed, and not active, hence getActiveScreen doesn’t return the screen you are thinking at. The getEventScreen() method however is correct. I will update the API doc to explain this subtle difference.
The second issue is that the script updates the item and forces it to be rebuilt, hence bindings are re-evaluated again, the script is run again, the item reloaded again, etc, forever.
I’ll fix the second issue in the next update, but you can make it work right now by using getEventScreen and using the resume event of the item instead of the binding.
]]>
< ![CDATA[
Pierre Hébert after the recent update I have tried both getActiveScreen().goToDesktopPosition and getEvent().getScreen().goToDesktopPosition. Non of them is working.
Following error occurs
At line 12: TypeError: Cannot find
function goToDesktopPosition in object
http://net.pierrox.|ightning_|http://auncher.script.api.b.b@d0dfb72.
]]>
< ![CDATA[
Abdullah Alahdal sorry, although I did test the api in debug build, I failed to do it in the release build. I didn’t notice that obfuscation were incorrectly applied on Screen classes in this build. Let’s hope it will be ok in the next update!
]]>