go to stack question

Judy Perry jperryl at ecs.fullerton.edu
Tue Apr 10 20:46:25 EDT 2007


Sue,

It may not seem obvious or intuitive, but try this:

Create one mainstack; save it as "Test-A.rev"
Create another mainstack; save it as "Test-B.rev"
Go to the first stack and create a button
Give that button the following script:

   on mouseUp
   go stack "Test-B.rev"

Save both stacks
Close the second stack
Now try clicking on your button.  Doesn't work, right?

Manually open the second stack via the menu:
  File -> Open Recent File

NOW, and this seems to be the crucial step, access that second stack's
inspector palette via the menu command Object -> Stack Inspector

In this window, name the second stack "Test-B.rev".
Save and close it.

Try the button on the first stack again; it should now work ;-)
Even though the *file* was already named with the correct name, Rev allows
you to name the stack reference something else, and the go stack command
was looking for that stack object's name methinks.

HTH,

Judy

On Tue, 10 Apr 2007, Sue Smith wrote:

> I realize this is a very basic question, but I can’t
> make it work. I need to go from the default stack A to
> a second stack B, and also close stack A. Does stack B
> need to be a substack of A? If so, is there a way to
> import it into stack A.
>
> Does anyone have any suggestions?
>
> Thanks!
>
>
>
>
> ____________________________________________________________________________________
> Need Mail bonding?
> Go to the Yahoo! Mail Q&A for great tips from Yahoo! Answers users.
> http://answers.yahoo.com/dir/?link=list&sid=396546091
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution
>




More information about the use-livecode mailing list