Error getting tags :
error 404Error getting tags :
error 404 stackFiles | revDocs | RunRev
Welcome Guest (Log in)
Product Edition
Expander triangle

set the stackFiles of stack to stackFileList

Platform Support
MacOS,Mac OS X,Windows,Linux
None required
Specifies a list of stacks and their file names, to be used when a stack that's not open is referenced in a handler.

set the stackFiles of this stack to "My Dialog,Custom Dialogs.rev"

Additional Comments
Expander triangle

Use the stackFiles property to make one or more stacks accessible to handlers, even if the stack is not already open or in memory.


The stackFiles of a stack is a list of stack references, one per line.

Each stack reference consists of the short name of a stack, a comma, and the name of the file that contains that stack. (Do not put a space after the comma, unless the file name starts with a space.)

By default, the stackFiles property of newly created stacks is set to empty.


When a handler or object refers to an object in a stack other than the current stack, Revolution checks all stacks that are loaded into memory (and their substacks) to find the referenced stack. If the stack cannot be found, Revolution checks the current stack's stackFiles property to locate the stack being referenced, and loads it into memory so that its properties and the objects in it can be used.

For example, if your stack contains a statement like this, the stack "Customers" must either be loaded into memory, or be listed in the stackFiles, in order for Revolution to know where it is:

get the width of field "Text" of card "Data" of stack "Customers"

In this example, if the "Customers" stack is not open and isn't in the stackFiles, the statement must refer to it by its full long name, including its file path:

get the width of field "Text" of card "Data" of stack "Customers" \

of stack "/Volumes/Data/Business.rev"

Using the stackFiles lets you simply specify the stack's name, instead of including its file path everywhere you refer to an object in the stack.

The stackFiles of a main stack is inherited by its substacks: if a handler in a substack refers to a stack that's not loaded, Revolution checks the stackFiles of both the substack and its main stack.

Important! Relative file paths in the stackFiles start from the folder that the stack is in, rather than starting from the defaultFolder as with other relative paths in Revolution.

Placing a stack in the stackFiles lets handlers in your stack refer to objects in the referenced stack, but does not automatically allow handlers in your stack to call handlers in the referenced stack's scripts. To use a stack as a library, allowing your handlers to call the stack's handlers, use the start using or insert script command.

User Comments
Expander triangle