On 4/13/05, Richard Gaskin <[EMAIL PROTECTED]> wrote:
> I had submitted an enhancement request to BZ some months ago for that,
> but for some odd reason I can't find it in there now
>
Maybe we need to add a BugzillaRequestNotHandled token. ;-)
Thanks for the info.
--
Regards,
Howard Born
Howard Bornstein wrote:
Is "the executionContexts" documented anywhere? I couldn't find a
reference to it in the online documentation.
I don't know.
Not sure where I learned about it, maybe from poking around the Rev
frontscripts.
To the best of my knowledge, there are only a very few tokens in u
On 4/13/05, Richard Gaskin <[EMAIL PROTECTED]> wrote:
>
> answer the executionContexts
>
Richard,
Is "the executionContexts" documented anywhere? I couldn't find a
reference to it in the online documentation.
--
Regards,
Howard Bornstein
---
www.designeq.com
__
Thank's Richard,
OK I found it. I might also mention that the
resulting Answer Box contents was as long as I have
ever seen. Oh my...
Kathy Graves Jaqua
[EMAIL PROTECTED]
___
use-revolution mailing list
use-revolution@lists.runrev.com
http://lists.ru
Great debugging tip, Richard.
It works on mouseUp in a button, so my guess is that something is
sending a second preOpenStack handler.
You could test that theory by adding this to the beginning of the
preOpenStack handler:
answer the executionContexts
If you see the answer box a second time
Kathy Jaqua wrote:
OK "1" more time, Maybe this time I will get it.
I set a customProp in my stack called cEnterToDoProp
This is the number of time the Stack is opened. (Like
how hard is this?:)
in a preOpenStack:
get the cEnterToDoProp of this stack
put it into tCount
add 1 to tCount
set the c
OK "1" more time, Maybe this time I will get it.
I set a customProp in my stack called cEnterToDoProp
This is the number of time the Stack is opened. (Like
how hard is this?:)
in a preOpenStack:
get the cEnterToDoProp of this stack
put it into tCount
add 1 to tCount
set the cEnterToDoProp o
