LiveCode Forums.

To save anyone time in viewing what transitions are available, here is a stack.

thank you very much

Thanks anmldr,

One thing though...
Some of the visual effects are buggy. When you include the official script for using them, for example: (the quotation marks around the name of the effect are not needed according to dictionary)
then you see the bugs that are reported here: http://quality.runrev.com/show_bug.cgi?id=12641
Check the reveal right as well with the code above

keram

I guess it depends on if you have variable checking on or not?

Linda

Hi Linda,

No, even with variable checking on you don't get any error when omitting the quotation marks in this case.

keram

Actually, does anyone know why the lock screen for visual effect and unlock screen with visual effect... parts of the script have been added?? What if we don't include it and create a mobile standalone? Will it create a problem?

keram

Hi keram,

keram wrote:Actually, does anyone know why the lock screen for visual effect and unlock screen with visual effect... parts of the script have been added?

only the RunRev engineers may know...

keram wrote:What if we don't include it and create a mobile standalone? Will it create a problem?

What do you think? Try it, cry and then tell us


Best

Klaus

I tried and cannot tell if there is any difference - it works in both cases.

Then you were lucky, usually iOS apps will crash when NOT using the official syntax!
Which shouldn't happen anyway!

But I am really wondering why you question the official syntax at all!?
Is your life so boring?

Klaus wrote:Then you were lucky, usually iOS apps will crash when NOT using the official syntax!
Which shouldn't happen anyway!

I tried with Android app. Right now I cannot test any iOS apps.

Klaus wrote:But I am really wondering why you question the official syntax at all!?

I'm not questioning the official syntax, only I want to use one of the visual effects that do not work properly with the official syntax and the bug has not been fixed. That's why my question.

The new syntax was introduced when image caching in the engine was implemented, somewhere in verion 6 I think. The engine now uses caching to speed up performance, and that required a change in how visual effects were used. The "for visual effect" addition tells the engine to cache the card image before applying a visual effect.

They should all work as advertised, so if they don't it's a bug. Which ones fail?

Hi Jacqueline,

jacque wrote: Which ones fail?

The ones with red buttons - basically all of them (see the attached stack). I cannot test the curl.
I added to the red ones: lock screen for visual effect/unlock screen with visual effect...
Compare with the corresponding ones without lock/unlock

BUT here is something that I've noticed after more careful reading of the Dictionary and the User Guide that perhaps you could confirm:

visual effect - from the Dictionary:
"When you issue a visual effect command, it is stored to be used the next time you navigate to another card in the same window with the go, find, or pop command. Usually, you place the visual effect command immediately before these commands in a handler, like this:

visual effect dissolve -- sets up the effect
go to card Index -- effect is seen during the go

[So here there is no lock screen used!]
...

"To execute a visual effect without moving to another card, lock the screen, make any changes you want to the card's appearance, and use the unlock screen with visual effect form of the lock screen command."



from the LC User Guide:

"Use the visual effect command to display a visual effect. To go to the next card with a dissolve transition effect:

visual effect dissolve slow
go next card

[no lock screen used!]

"To make changes to objects on the screen with a visual effect (e.g. hide, show or move them), first lock the screen, then make the changes, then unlock the screen:

lock screen
hide image 1
show image 3
unlock screen with visual effect "wipe right"

----

So from these it seems that lock screen etc is only necessary when hiding, showing, moving objects on the same card. In that case all the effects in the attached stack would be working OK since they all go to next card.
Is that correct?

keram

The navigation effects were grandfathered in after the new caching scheme was implemented. I think they mostly still work but I haven't tested them all. The engine is probably doing the lock/unlock for you in the background.

The curl effect requires QuickTime, and I'm guessing some of the others you say don't work also require it. (I don't usually download and examine stacks so I haven't looked at yours.) QT is deprecated now, so LC ships with it disabled. You can re-enable it with:

set the dontUseQT to false

But many Windows users won't have QT installed, no mobile devices will, and eventually it may be discontinued on Macs.