On 12/30/17 4:06 PM, Sannyasin Brahmanathaswami via use-livecode wrote:
# theoretically 1/5 of 2000 = 400 milliseconds
why is the script profiler saying this line takes 4765 milliseconds top execute?
If it's like the MC profiler, these are relative times. They aren't
meant to tell you
It may also help to lock the screen for visual effect within a given rectangle,
thereby reducing the number of pixels that need to be updated. If the images
are of equal dimensions and with the same loc, you can refer to the rect of one
of them, otherwise you can have an invisible graphic as
So: if the effectRate defaults to 2000 (which is what I'm seeing here on
desktop) and you have
--
Show image "grand-canyon" with visual effect dissolve very fast
---
# theoretically 1/5 of 2000 = 400 milliseconds
why is the script profiler saying this line takes 4765 milliseconds top
Sannyasin Brahmanathaswami wrote:
> Yikes! 2.5 seconds for dissolve very fast on a 120k image…
>
> given the new look and feel of apps where transitions are
*everywhere* … this takes waaay to long…
>
> is there any way to optimize this?
Effect durations can be normalized and fine-tuned using
Appropo optimization thread, I'll dig in on specific issues
The script profiler is showing this
for a script that runs super fast until:
1433 868 show image "gems-image" with visual effect dissolve very fast
So this was pertty long but I suppose reasonable enough…
then, I ran it
