Hi Jim,
The Variable Watcher indicates that the value of the incoming variable is
correct, and remains so throughout the execution (or the VW is not updating
properly). Nevertheless, the 'close stack' kills the utility of the
variable.
-- Paul
On Sat, Mar 1, 2008 at 11:58 PM, Jim Ault [EMAIL
According to the docs, the stack should not be purged until the handler(s)
finish, so the variable should remain available to be passed. If you tried
to open another stack with the same name, Rev should complain.
I do know that complex send systems can create 'folds' in the message path
that no
I'm building a stack that is a data entry app for a daily journal. Once the
day's entries have been posted (emailed to myself), I want to store them in
the stack. I came up with a scheme of prepending j to the seconds
representing the day and using that as the name of a custom property. No
problem
First, use the stack inspector to confirm that your property is indeed the
value you think it is.
Do this by opening the stack inspector, then choose the custom properties
drop down. Now inspect the values:
set the jDate of this stack to 99/88/77
then
put the jDate of this stack into tJournal
Problem solved, but I don't know why.
If I pass jDate with the j already prepended, it works.
-- Paul
On 3/1/08 9:32 PM, Paul Foraker [EMAIL PROTECTED] wrote:
I'm building a stack that is a data entry app for a daily journal. Once
the
day's entries have been posted (emailed to myself),
Thanks, Jim.
Yes, I have confirmed in the inspector that the property exists, and as I
mentioned, the correct data is retrieved in the Message Box, but not in the
stack script.
The variable jDate is composed of the letter j and the seconds for the
date. I delete the j when I want to convert the
Paul Foraker wrote:
I'm building a stack that is a data entry app for a daily journal. Once the
day's entries have been posted (emailed to myself), I want to store them in
the stack. I came up with a scheme of prepending j to the seconds
representing the day and using that as the name of a
Turns out the problem was in the calling handler, but this is a little
weird. When I reported just now that I'd fixed it by passing j already
prepended to the seconds, I had only tried that from the Message Box. Back
inside the calling script, it didn't work. Here's the calling script in a
button
I am not sure I am on the right track here, but it seems the 'close stack'
is working as I would expect in your example.
When you start a script using a handler in a stack, you should not be able
to close that stack before finishing the handler, including all of the
function and handler calls.
