Archives
now browsing by author
I have a dummy binding on a shortcut in a folder that provides a dynamic calendar date icon for the associated app.
However, the last time this ran properly was on 5th October. There must have been an alpha release on either 5th or 6th October that broke it.
The problem seems to be that parseInt(n) on a number with a leading zero (such as that returned by $ll_day) now results in NaN. Adding a second parameter of the form parseInt(n, 10) fixes the problem.
Is this intended new behaviour or is it a bug?ο»Ώ
]]>V14a11
Editing properties of script-created items prevents other later scripted edits to work.
E.g. The color of items can’t be set via script once the item has been styled initially (accessing the properties seems to be enough already) via script before the color change is applied.
The color change works (without any code change) if no styling via script happened at the time the item was created.
]]>Hi, it’s been a while since my last post here.
It’s about: screen lock.
for 3 years (since my froyo phone) I use app to lock my phone without touch the power button and use it to replace “double tap to sleep” feature on my kitkat (upgraded to lolipop) stock launcher.
But now I use Marshmallow phone with fingerprint sensor. And I see many people struggle with it when tried screenlock app (or launcher with lock shortcut feature).
I search many lock app in playstore but always come to unpleasant statement like “not compatible for fingerprint phone”, “not compatible for marshmallow phone”, or “not compatible for nougat phone (what?)”.
So anyone can help me to tap for locking my phone again like old times? It’ll be good if I can achieve it with mere script.
This limitation forced me to stay with stock launcher.
And again, sorry for my poor english π
Thank you
]]>Not sure if this a bug but when opening the activity screen to edit the settings like layout or events of a desktop,…
You would assume the desktop paused would be fired instead.
]]>V14a10
Setting the alpha of an item lower than 255 leads to text aliasing artefacts when zoomed into the desktop although hardware acceleration is disabled for desktop and item
You would expect a clear text with sharp edges as long as hardware acceleration remains disabled.
Example script
getEvent().getScreen().getCurrentDesktop().getItemByName(“item”).getProperties().edit().setInteger(“i.alpha”,254).commit();
]]>V14a10
A script executed after desktop items have been removed throws nullpointer exception.
_____________
var items = getEvent().getScreen().getCurrentDesktop().getAllItems();
var l_item;
var d =getEvent().getScreen().getCurrentDesktop();
for(var i=items.length-1;i>=0;i–)
{
l_item=items[i];
d.removeItem(l_item);
}
getEvent().getScreen().runScript(“event”,null)
___________
The script “event” only displays an android toast message.
BTW: the desktop consists of items created by script. Executing the same script on the default desktop works. ο»Ώ
]]>LL crash when refreshing the app drawer (or when unistalling app, but I guess the refresh caused by the app removal…
Log sent.
]]>
D5 Creation