hi All, hi Pierre Hébert

hi All, hi Pierre Hébert 

since a few days i play around with bindings.

It’s a very nice feature but i have a lot of weired problems.

https://plus.google.com/u/0/+gerdreuter/posts/aCUgkJx58Hc

and now new problems.

i’ll try to do some pretty animations and also want to use tasker to show notification counts.

please watch the demo-video, to see hat i mean.

following weired things happens:

after reboot or restoring the template the position and size of the items are different. also the value of the variables (particularly the variables filled by tasker) are lost.

Please look at the pictures.

Any suggestions, solutions?

edit:

LL 12.5.2

Android 5.0.2 

]]>

6 Commentsto hi All, hi Pierre Hébert

  1. Anonymous says:

    < ![CDATA[

    found a solution by myself for the “number” problem:


    8 instead of 8.0



    var z= … (add formula);


    var za=z.toString();


    return za;

    ]]>

  2. Anonymous says:

    < ![CDATA[

    workaround which should not be the solution:



    before add bindings set the items to the final position, do all other setting for the items.  after this add the bindings.



    in my case the items will still loose the y-postions, because all variables are lost, but i start a script at event load (desktop), where i set the variables and start a taskertasks which sets all ll_variables to the current values.



    ;-(((

    ]]>

  3. Anonymous says:

    < ![CDATA[

    I think the problem is that you are not in latest beta (which is understandable).


    I’m saying this because there were some fixes regarding bindings.

    ]]>

  4. Anonymous says:

    < ![CDATA[

    TrianguloY could be a reason. hope a new stable will fix this problems.

    ]]>

  5. Anonymous says:

    < ![CDATA[

    gerd reuter nice job gerd 😊


    Is there no icon if count = 0 ?

    ]]>

  6. Anonymous says:

    < ![CDATA[

    Bruno-Isa LAMOUR-ARNOULD


    icons slide up/down. counter only visible when greater 0

    ]]>

Leave a Reply

Your email address will not be published. Required fields are marked *