V14a5 alpha
V14a5 alpha
Edit: and V14a6, then V14a7 🙂
Yet another round of bug fixes, but not only.
Leveraging the new architecture, this update feature several optimizations which should noticeably reduce the startup time of the app drawer, as well as the home screen. I’m curious to know how it works for you.
Full ChangeLog: http://www.lightninglauncher.com/wordpress/change-log/
]]>« Howdy, new LL user here. (Previous Post)
(Next Post) I noticed when I changed the tinted background my widget resize how can I fix this problem »
D5 Creation
< ![CDATA[
wow , downloading and testing
]]>
< ![CDATA[
loading the home screen is immediate !
seems app drawer quicker 🙂 but I don’t use so much
]]>
< ![CDATA[
Big crash immediately upon entering edit mode. Report sent.
]]>
< ![CDATA[
Wow. I use the app drawer a lot. It’s much much quicker. Entering edit mode works fine on my phone. No crash.
]]>
< ![CDATA[
Roger Schreuders thanks.
I’ll see if I can sort it.
]]>
< ![CDATA[
Working very well Pierre Hébert noticeable improvement. 👍 And no crashes so far..
]]>
< ![CDATA[
Chris Chastain thanks for the report, it helped me to fix the issue: it only appears when entering edit mode and edit bars are initially hidden. An update is coming very soon 🙂
]]>
< ![CDATA[
With the lockscreen i have a little issue. In the moment i have 2 active launchers. LL and Total Launcher. Although LL is set in my Android settings as standart launcher, after unlocking the lockscreen of LL, Total Launcher pops up, and not LL. If i touch the home button, LL starts.
It’s not a big thing. I just noticed it.
Edit: after a reboot it works correctly 👍
]]>
< ![CDATA[
Pierre Hébert great… Was just just coming back to say that! 😁
]]>
< ![CDATA[
I can see exactly the same thing when developing. This is due to app restart. I think that after a reboot the issue will disappear.
]]>
< ![CDATA[
Pierre Hébert with v14a7 script which I send you template causes possibly recursion when used in binding and in resume event.
Second issue: try to run following script a) from lightning menu ; b) from tasker:
var it = getEventScreen().getItemById(8192003);
Android.makeNewToast(“item: ” + it, true).show();
8192003 is a valid item is from shortcut.
a) shows item: Shortcut ‘Name’ 8192003
b) shows item: null
I think the screen returned by getEventScreen() from tasker event has in fact no items. How can I address a specific item in new api? In v12 LL.getItemById() did the job.
]]>
< ![CDATA[
Fixes are rolling out hot and heavy! Thanks Pierre Hébert!
]]>
< ![CDATA[
How to use the new Lighting object?
Doesn’t seem to be known in script code suggestion and LL has to be used to call eg getCurrentDesktop(). Otherwise “not defined error”
Running on 14a7
Where to sent crash reports by the way? What is the correct email address? The crash window points to invalid pierrox@pierrox.net
]]>
< ![CDATA[
+Mirko Kohler yes, I can see this too. I’ll try again to break the recursion. Regarding the script run from Tasker, I suspect it is run in background, right? In that case there is no real screen, and no item. That’s quite dumb. I’ll see what I can do for that.
Karsten Franke you don’t have to use it explicitly, you just have to call its methods, because this is the root object. LL.getCurrentDesktop() has no direct equivalent in Lightning but you can use getConfiguration().getCurrentDesktopId() or getEventScreen().getCurrentDesktop() if the screen is the home screen. I’ll probably move this “Screen.getCurrentDesktop” method from the “HomeScreen” class to the “Screen” class so that it can be called for the other types of screens too.
The address pierrox@pierrox.net is valid. Did you get errors with it ?
]]>
< ![CDATA[
Understood with the lightning object.
Email couldn’t get delivered initially, seems to work now though.
]]>
< ![CDATA[
is android.graphics.Paint.setColor unsupported now? was still working in a4
]]>
< ![CDATA[
There’s no reason for it to fail, since it’s in the android framework. What kind of error do you get?
]]>