Jim,
actually use my own flag since i sometimes leave debugging stuff
turned on in the standalone when wanting to track things in the
standalone or kill loops problems when they show up there. also
sometimes want these turned off when in the development environment
for testing before moving to a standalone. its useful to be in
control of this flag. usually have a toggle button for it on the main
card until near the end of development to allow these functions to be
turned on and off until near the end of development.
cheers,
jeff
Jeffrey Reynolds
On Jun 27, 2006, at 5:54 AM, [EMAIL PROTECTED]
wrote:
you could also use the built-in
if the environment is "development" then showDevelopOptions
hate stripping code when i am already through part of testing to easy
to screw something up that was working perfectly well and then theres
usually that one gotcha later in testing that its nice to have your
early debugging stuff still there and available for use in figuring
out what is going wrong... I also use it to pass results repeat end
numbers and other variables into a displayable field so i can easily
watch what is going on in more complex scripts that need tweaking.
again only displayed if the field is show and the development mode
variable is set right.
_______________________________________________
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
