visual effect between stacks

[dunbarx]

I have never needed to use a visual effect, though have played around a long time ago.

No problem between cards on a stack, but cannot make the visual effect, er, visual, between stacks. This comes from a thread:
viewtopic.php?f=8&t=35826

Anyway, with two stacks "a' and 'b", from a button on "a', this navigates, but without any visual effect:

Code: Select all

on mouseUp
   visual effect "dissolve"
   go stack "b" in new window
end mouseUp

There is a delay, the same as if the effect was in fact doing its thing. No other gadgetry, locking/unlocking the screen for visual effect, say, matters.

This is why I am back in the beginners section.

Craig

[jmburnod]

Hi Craig,
I remember used the blendlevel property of stack "b" to simulate a visual effect dissolve.
Jean-Marc

[richmond62]

Code: Select all

on mouseUp
   put the windowID of stack "STAKKK" into STKID
   visual effect "dissolve"
   go stack "NOOO" in window STKID
end mouseUp

Works.

[dunbarx]

@Richmond.

Thanks, but not for me.

Again, there is a delay one would expect from the visual effect process, but no actual effect

On Mac.

@ Jean-Marc.

Makes sense, but the dictionary states that one can use visual effects when navigating from one stack to another using the "go" command alone. You post implies a kludge is required. Is that in fact so?

Is this just a dictionary error? Or more likely, just me?

Craig

[Klaus]

Hi Craig,

it definitively works, however only on a "per stack" base, not with different windows!

Code: Select all

...
visual effect "dissolve"
go stack "b" in new window
...

Doesn't work!

1. the two stacks must have the exact same dimensions w/h
2. use the official syntax:

Code: Select all

...
lock screen for visual effect
go stack "b" in window of this stack
unlock screen with visual dissolve
...

Tested and works!


Best

Klaus

[FourthWorld]

Code: Select all

   go stack "b" in new window

The "in new window" clause interests me. Perhaps we have an opportunity to enhance the docs.

Craig, what was your intention in adding that clause?

[dunbarx]

Richard.

Craig, what was your intention in adding that clause?

None. I have never "used" a visual effect, though played around with them way back in the day. This derived from the other thread.

Craig

[dunbarx]

Rereading the dictionary, I can see that it sort of implies being limited to stacks that are "folded" into the same window.

It threw me though.

And so Jean-Marc's kludge is just that, something that will do the job really and truly between two separate stacks, each to their own. Good to know how these things work...

Craig

[jmburnod]

Thanks Craig to examine deeply this case and refresh my memory
Best
Jean-Marc

[richmond62]

HyperCard was concieved off as a single-windowed arrangement with a stack of cards metaphor.

LiveCode has inherited that metaphor. but also introduced the concept of substacks; therefore
allowing the possibility of multiple windows for a single application.

The visual effect transitions have also been conceived as things that happen between cards in the
same stack, so it should come as no great surprise that attempting to use them between stacks
is beset with problems.

[jacque]

The visual effect transitions have also been conceived as things that happen between cards in the
same stack, so it should come as no great surprise that attempting to use them between stacks
is beset with problems.

It's officially supported, and using the window ID is the only way to use visual effects to navigate between two stacks. But use the syntax Klaus suggested. Also, I usually use the window ID rather than "this window" though apparently that works.