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();

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. 

Neither of these work with v14a8

getEvent().getContainer().getAllItems()

getEvent().getScreen().getCurrentDesktop().getAllItems()

In V12 I used LL.getCurrentDesktop().getItems() which doesn’t work now either

Assign this script to a shortcut:

LL.getCurrentDesktop().getProperties().edit().setString(“scrollingDirection”,”AUTO”).commit();

And notice a short flashing. Seems like the screen gets refreshed quickly? Doesn’t look great though.

New behaviour introduced with v14a

Additionally, the container scrolls to top when the script gets executed. I would expect the container remains in its scrolling position until an explicit setPosition().