Going from a very widget heavy desktop (5 complex ZWs), to one without many (0 ZWs) sometimes results in a failure…
Going from a very widget heavy desktop (5 complex ZWs), to one without many (0 ZWs) sometimes results in a failure to clear / redraw. I don’t have this issue pinned down very specificity (sorry).
]]>
D5 Creation
< ![CDATA[
Seems to be something with the background picture. Sometimes I had the same issue with the wallpaper: it doesn’t render properly.
]]>
< ![CDATA[
Yes, the system wallpaper tends to fail on some devices. It is usually not apparent because almost all other launchers do not use the system wallpaper directly. Reboot and the problem will vanish…
]]>
< ![CDATA[
Okay, so I’ve done some testing: The problem, when it happens, actually occurs on every desktop with a wallpaper (transparent background). Rebooting doesn’t help (not the one time I did it anyway). Killing (restarting) LL does help, at least for a while.
]]>
< ![CDATA[
That’s a bit weird: since rebooting has restarted the app, I would have expect a similar effect. There is a thing that you can try: set wallpaper width and height to 0 first (if these values were not 0) then try to select a “per desktop wallpaper”
]]>
< ![CDATA[
It is odd. I think it has to do with LL being swapped out from memory. During a reboot a lot is happening, and with many things vying for memory, maybe LL gets swapped (and thus buggy).
My width and height have been set to 0 (auto sized), but I don’t understand this “per desktop wallpaper”. I’ve looked through the settings quite a bit, but I don’t see any way to set the wallpaper except “Customize Lightning”->”Current desktop”->”Wallpaper & background”.
]]>
< ![CDATA[
Please install http://www.pierrox.net/cmsms/uploads/files/android/applications/Lightning%20Launcher/attic/lightning_launcher_native_image-1.apk, the option will magically appear (sorry I forgot about that, the plugin is not on the Play Store).
This issue is a longstanding one. I know for sure that the problem is in the Android component that merges surfaces (layers). Now, there is certainly something in LL that help to trigger the problem. Unfortunately I don’t know what. I know that it can be reproduced quite frequently on a Nexus 7, and by chance I own a Nexus 7 but… until today I have been unable to reproduce it on my device, grrrr… Once I can trigger the bug reliably, I should be able to add a workaround.
]]>
< ![CDATA[
Michael Plotke good news, another guy helped me to find a way to reproduce the problem. The problem is now clearly identified and I have a workaround !
The bug will appear when the app is started with a fully opaque background color and then switch to a translucent background.
The next update will fix this case.
]]>
< ![CDATA[
Thanks so much! Glad you found the cause.
]]>