New update completely messed up my set-up.
New update completely messed up my set-up.
I had script changing the position of some panel. Now they all change the position of the main desktop instead.
I had script on slide left ad right to move the desktop to a fixed position, it no longer works either.
I can’t access a lot of my set-up due to that.
I use a Nexus 6P without Android Nougat since the OTA update is not yet released.
]]>
< ![CDATA[
I think the getcointainerbyID function that I used got nerfed
]]>
< ![CDATA[
Also widgets can’t load anymore
]]>
< ![CDATA[
Did you read the changelog?
]]>
< ![CDATA[
Yes I did. I tried removing the LL even though it was still supposed to work. If I do so the script fail. If I don’t, the script just do not work.
And even though, I’d expect the final update to be seamless for users. So in alpha it is OK to have screwed set-up like that, but this must be corrected before final release.
]]>
< ![CDATA[
Remember… This is an alpha release, even though it says beta in playstore.
Did container ID get changed perhaps?
]]>
< ![CDATA[
I’m having some unexpected behaviour with a simple script similar to yours.
I have some folders who’s positions are set back to 0,0 on load and resume.
My desktop is instead set back to 0,0
]]>
< ![CDATA[
I have the same problem.
i use a lot of ‘getContainerbyId’ ,but all behavior return to container id ‘0’.
//example
//var d = getCurrentDesktop();
var con = getContainerbyId(100);
con.setPosition(500,500,1,true);
//end
the id ‘0’ position moved, but id ‘100’ didn’t move.
]]>
< ![CDATA[
Good! I’m glad we all have the same results!
I mean not GOOD really, but… You know.
]]>
< ![CDATA[
Chris Chastain LoL
I’m sad now because my all LL templates doesn’t work preferably….
I have to rewrite ALL script..
]]>
< ![CDATA[
New update didn’t correct that issue.
]]>
< ![CDATA[
Got the new update. Script fixed for me.
Great work as usual.
]]>
< ![CDATA[
Tried a reboot seems the issue with widgets taking hours to start is fixed as well.
]]>
< ![CDATA[
Fixed my minor script issue also.
]]>