Hugh,
Jacque has probably hit the correct answer for you case. The 'set
script' strategy would work if the new group script was a call to a
compiled function in another script in the hierarchy. If your idea
was to customize the script, then set the script of an object to that
script, you should consider writing the compiled handler with
branching or params to handle variations.
Hope this helps.
Jim Ault
Las Vegas
On Apr 8, 2009, at 1:13 PM, J. Landman Gay wrote:
Hugh Senior wrote:
I have a protected stack that creates a window and a group, then
sets the
group script. Works a treat. When run as a compiled application
exe, it no
longer sets the script (I know this because an answer dlog that
should
display the script comes up empty instead).
The only thing I could think of is that the window it creates is
somehow
protected as well, but a similar answer dlog confirms that the
passkey of
the new stack is empty.
Any clues or insights? Am stuck.
You've probably hit the script limits. In a standalone, you can't
set a script that has more than 10 lines.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
