On 6/26/06 4:06 PM, "Jeffrey Reynolds" <[EMAIL PROTECTED]> wrote:
> i have always done this plus a flag for a development variable and > dont bother stripping them later, they only work if the variable is > set right (by me when in development mode). > > global isitdev > if the optionkey is down and isitdev is "yessirrebob" then exit > [handler] 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. Jim Ault Las Vegas _______________________________________________ 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
