Re: Dissolve/Transitions Very Costly
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 exactly how long an operation takes, just how it compares to others. The profiler itself slows down execution. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Dissolve/Transitions Very Costly
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 reference or just the local screen coordinates where you would like the effect to take place, like this: lock screen for visual effect in rect(rect of image “test1”) — or the direct coordinates as param (200,200,500,400) hide image “test1” show image “test2” unlock screen with visual effect dissolve very fast Regards Tore Nilsen > 30. des. 2017 kl. 23:06 skrev Sannyasin Brahmanathaswami via use-livecode > : > > 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 > execute? > > The dictionary has two methods: if you look up "show" it appears you should > be able to perform this "directly" > > But, under the visual effect command the suggested method is to lock screen, > make the change then unlock the screen with visual effect. And we get > different results, various conditions where the effect just does not happen > anyway…no fadein as expected… there is a delay… screen is "stuck" and > suddenly the image changes. > > hopefully this all improves very soon as CSS Animation which is fast and > smooth… now dominates UI everywhere, even for small inconsequential UX ops… > designers are expect all kinds of "oozing" warp,slide,fade away etc. > > Frankly I'm sure users care that much, and if you have a very strong content > component, it's a lot more compelling than having your address book "zip up" > when you close it. And what I'm here is that the most important thing is > stability and performance. So, I may just remove all these dissolves. > > > Richard wrote: > >Effect durations can be normalized and fine-tuned using the effectRate >global property. > > > > ___ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Dissolve/Transitions Very Costly
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 execute? The dictionary has two methods: if you look up "show" it appears you should be able to perform this "directly" But, under the visual effect command the suggested method is to lock screen, make the change then unlock the screen with visual effect. And we get different results, various conditions where the effect just does not happen anyway…no fadein as expected… there is a delay… screen is "stuck" and suddenly the image changes. hopefully this all improves very soon as CSS Animation which is fast and smooth… now dominates UI everywhere, even for small inconsequential UX ops… designers are expect all kinds of "oozing" warp,slide,fade away etc. Frankly I'm sure users care that much, and if you have a very strong content component, it's a lot more compelling than having your address book "zip up" when you close it. And what I'm here is that the most important thing is stability and performance. So, I may just remove all these dissolves. Richard wrote: Effect durations can be normalized and fine-tuned using the effectRate global property. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Dissolve/Transitions Very Costly
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 the effectRate global property. -- Richard Gaskin Fourth World Systems Software Design and Development for the Desktop, Mobile, and the Web ambassa...@fourthworld.comhttp://www.FourthWorld.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Dissolve/Transitions Very Costly
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 again. 1433 2526 show image "gems-image" with visual effect dissolve very fast 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? ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode