Use loader (splashscreen) approach, then you won't not need to compile
your password protected stack: create invisible stack, point it to your
stack and put
on startup
go stack "yourstack"
end startup
into its script.
Compile this stack. Run it. That's it.
You may rename extensions of stacks from .rev to .lib
Regards
Viktoras
[email protected] wrote:
The problem is that I cannot build the standalone !
Regards
Camm
---- "viktoras d." <[email protected]> wrote:
What if you put the offending answer into a "try.... end try" structure
and handle the error yourself when it fails?.. At least it should not
display error dialog to end user.
Regards
Viktoras
AS A REMINDER :-
ALL IS OKAY ON 2.8 WITH STANDALONE PASSWORD SET
ALL IS OKAY ON 3.0 WITHOUT STANDALONE PASSWORD SET
Regards
Camm
---- "J. Landman Gay" <[email protected]> wrote:
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
