now browsing by category
Pierre Hébert Bug/Unexpected Operation.
My setup involves several Variables in Tasker, KLWP and LL to coordinate position and visibility of shortcuts, folders and items both in LL and KLWP. I am using the variables in property bindings in LL. No scripts are involved.
What I am seeing is that if the bindings involve position (off grid) of the items they don’t always work. Immediately after a reboot it seems to work for a little while.
If I open the APP draw or go into Editmode in LL and exit, the desktop and all items will be displayed correctly.
Another thing I have observed is on occasion when variables are changed the entire desktop will flash and repaint, and then everything works as it should. BUT if I look in the recent items folder (in Android) I will see LL as a recent app. If I leave this there, everything works normal. If I kill the app, it goes back to not working.
I have tried the “keep Lightning running” option with no change.
I had none of this behavior prior to v14. Nexus 5x 7.0 Sept Security Update.
]]>Testing new screen API getitembyid() to retrieve a folder within a panel without traversing the complete hierarchy.
//Get the id of the folder
id=getEventScreen().getCurrentDesktop().getItemByName(“panel”).getContainer().getItemByName(“folder”).getId()
//Doesn’t open the folder by accessing the folder directly without traversing the hierarchy (which would be elegent)
getEventScreen().getCurrentDesktop().getItemById(id).open()
//Does open the folder. but is tedious and hard-coded hierarchy which I would want to avoid
getEventScreen().getCurrentDesktop().getItemByName(“panel”).getContainer().getItemByName(“folder”).open()
]]>14a7/14a4 – LL crash – http://pastebin.com/2b85ryuB
14a7/14a4 – LL crash – http://pastebin.com/2b85ryuB
LL 14a2 – no crash
]]>Running a script with LL.runScript from another script results in LL.getCurrentDesktop() to be null
– Android Version : 6.0.1
– Device : Sony Xperia Z3 compact
– Steps to reproduce the issue :
create a scriptA containing: LL.getCurrentDesktop().setPosition(100,100,1,TRUE)
Create script B containing:
LL.runScript(“scriptA”,null)
assign scriptB to home-key.
Pressing the home key does not animate the desktop. No action. Instead error of null object reference. (unexpectedly)
Setting scriptA to home-key does animate the desktop as LL.getCurrentDesktop() is not null (as expected)
]]>It seems that on the Samsung Note7 the installed Email client widged causes a crash everytime I try to add it.
14a7
Pierre Hébert
Deleted all but one desktop under ‘configure desktops’.
But there are remaining orphaned desktops all with the same name. See Screenshot of hierarchy view.
Expected result is only one desktop in hierarchy view as in desktop overview.
]]>This is a second try to explain/report a bug that’s exists on my phone for.
I try to give as many info as i can with screenshots.
I Have a Cubot H1 with stock, but rooted, Android v5.1, stock kernel 3.10.65+. No exposed or mods.
In one screenshot there is a overview of my display preference.
I tinted the statusbar and displayed gridlines so you can see better what happens.
In the first screens (A1-A3) the statusbar and content overlap are off. As you can see i get a tinted area exactly under the statusbar. Also the displayed screen is shifted downwards.
I edit mode the top area is always cluttered/overlaped with the menu overlay.
All the other screens are the same but with one option different in the systembar settings.
I hope you find something Pierre.
Screenshots are here:
https://www.dropbox.com/sh/c23dk97n277of4z/AAC8zzsPdcBcsYO7T-lamDn8a?dl=0
]]>I’m having a problem creating widgets.
In logcat, (link below), it appears to be a java error, but I’m not sure if it’s LL or my ROM (MM-based Resurrection Remix).
It seems to go away after a clean flash of the ROM, but then comes back within a few days of use (and LL tweaking).
Also of note: the problem is specific to LL. I do not have any problem creating widgets in Trebuchet (stock Cyanogen launcher) or Nova.
Update: I’ve also tried changing back to (the latest, now) alpha, and the problem persists in LL.
Any guidance/insight would be GREATLY appreciated.
—–
Logcat: https://www.dropbox.com/s/7yfqy6e24v3c2ok/2016-09-15-23-14-52.txt?dl=0
]]>