I have two stacks. The main stack (stack1) is my application. The substack (stack2) is a setting stack where I can change default values on my main stack. These values are stored in a file.
When I open my main stack, I read my settings file to retrieve the default values. This is working great.
My problem occurs when I change the values in the setting file (stack2)and try to update the values in the main stack (stack1). Changing fields works as I use the put command and specify the stack
put tFiles into field "Files" of stack "stack1"
Is there anyway to use the same logic with the hilite command?
ie. hilite button option1 of stack "stack1"
If the above isn't possible, what is the best way to "refresh" my main stack to pull in the most current values? Should I close/open the stack or card again?
Transfer Hilite Button Value From Stack To Stack
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
Hi warrenk
The only thing here is hilite, or any other parameters changed, won't be saved when (if) you make your stack into an application.
The solution there is to make your mainstack an About box, or even a Hello screen (or blank!) then your main app stack becomes a substack, and your setting file becomes the second substack. That way, when you save it as an application, you can specify that only the first mainstack is the application and all other stacks (substacks) are to remain as stacks, so that your main (sub)stack will "remember" any changes.
Hope that's sorted it for you.

No probs there:Is there anyway to use the same logic with the hilite command?
ie. hilite button option1 of stack "stack1"
Code: Select all
hilite button "option1" on card 1 of stack "Untitled 1"
The solution there is to make your mainstack an About box, or even a Hello screen (or blank!) then your main app stack becomes a substack, and your setting file becomes the second substack. That way, when you save it as an application, you can specify that only the first mainstack is the application and all other stacks (substacks) are to remain as stacks, so that your main (sub)stack will "remember" any changes.
Hope that's sorted it for you.
