v10.5b3
v10.5b3
Just a small update to fix some blocking issue:
– workaround for launcher stuck in extremely large grid drawing
– add LL.getScriptById
– add a dedicated Item name property: it replaces the item label, except for shortcuts. Existing methods Container.getItemByLabel, Item.getLabel and Item.setLabel still work but are deprecated. Existing scripts should not be broken. Use getItemByName, Item.getName and Item.setName instead.
This last modification is a bit sensitive. I tried to make enough tests to be confident that it won’t break anything, but my tester skills are quite low 😉
]]>« I’m making a more user-friendly & easy-to-use API for Tasker, I wanted to have your reviews on it. (Previous Post)
(Next Post) http://www.pierrox.net/ »
D5 Creation
< ![CDATA[
Works fine now, thank’s !!
]]>
< ![CDATA[
Thanks a lot.
Why 10.5b3? Any beta stuff to hunt for? 😋
If additions work, will they be released as 10.4.x or just as part of 10.5?
]]>
< ![CDATA[
This is the third beta in the 10.5 round. And there are plenty of beta stuff to test 🙂
All in one I believe it is rather “stable” but new features are quite “open”, hence it may (and it already has) raise issues and ideas.
The getItemByName stuff is also worth keeping an eye on it. It involves migrating data and it also has a subtle behavior in order to keep compatibility with older scripts while deprecating some methods.
]]>
< ![CDATA[
Just tested 10.5b3 on my tablet and loaded my template. Is the ZW scaling hack included? It seems ZWs work better after applying. They are too small since scaling is still 50%, but changing that to 87% (weird, expected other value) they seem okay. If I remember correctly, before they weren’t, had to reload every single one.
]]>
< ![CDATA[
Strike that, I was wrong, hack is not included, 50>>87 is as it should. Any chance we can get that right and included? Too bad I can’t test properly without an 1080×1280 device.
]]>
< ![CDATA[
I confirm the hack is not in b3. But I hope to have it included in b4 although it would probably be better to make a release and reopen a new beta with the scaling hack only.
I spent a lot of time on this and I discovered some key things: the scale must not be computed the same way, depending on from / to devices characteristics. It seems that if the computed physical screen size (not real screen size) is reduced zooper acts differently from when the sizes are equal. I have yet to determine how it behaves in other situations.
Overall, I hope that I am near from the solution.
]]>
< ![CDATA[
Pierre Hébert Great news. Let me know if I can assist in any way.
]]>