Since latest beta versions, I think it worked in the stable but I’m not 100% sure, when using image.update() to show…

Since latest beta versions, I think it worked in the stable but I’m not 100% sure, when using image.update() to show the changes on a image it doesn’t work. Or maybe there is a change I didn’t noticed that makes it to don’t update correctly.

The steps are simple: run this script made by you Pierre Hébert​ 😉 http://www.pierrox.net/android/applications/lightning_launcher/wiki/doku.php?id=script_paint_free_hand

]]>

6 Commentsto Since latest beta versions, I think it worked in the stable but I’m not 100% sure, when using image.update() to show…

  1. Anonymous says:

    < ![CDATA[

    Thanks, I think I know what the problem is. This is due to a drawing optimization which is now turned on because of more hardware accelerated operations in the beta. The app requests a refresh of a view but Android “thinks” that some part of the view didn’t change, and skip the redraw. This should be fixed easily.

    ]]>

  2. Anonymous says:

    < ![CDATA[

    This bug is fixed, but now there is another one!


    You start drawing, and it works fine, but after three/four drawing loops (two/three seconds drawing) the image is reseted (background removed and line started again.



    Also, when I try to run the script on a new item, it crash O.o

    ]]>

  3. Anonymous says:

    < ![CDATA[

    If you remove the old sketch panel and create new ones it should work. For the crash I think it is unrelated (a bad configuration).

    ]]>

  4. Anonymous says:

    < ![CDATA[

    Sorry but no.


    First time, the launcher gets unresponsive and I need to force close.


    Second time it crashes with the crash I sent to you

    ]]>

  5. Anonymous says:

    < ![CDATA[

    🙁


    I’ll come back to the emulator.

    ]]>

  6. Anonymous says:

    < ![CDATA[

    I finally found the issue (the first one at least). This is an old bug that only surfaces now 🙁 A workaround (which isn’t exactly a workaround) is to set the option “Image pool size” to 0 until I fix the bug.

    ]]>

Leave a Reply

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