--- In [email protected], sgp <[EMAIL PROTECTED]> wrote: > > MoreCommandsAsScript executes commands in the More > Commands edit box as a script, which allows you to use > loops, jumps, if-elseif in More Commands. I believe > that when PowerPro finds MoreCommandsAsScript it > copies the commands to a temporary file on the hard > disk and runs the file as a script. You may be able to > find such files in the PowerPro folder, look for > _MoreCmd_*.txt where * is a number. In more recent > versions of PowerPro you can dispense with using > MoreCommandsAsScript even for simple conditionals, > such as one line IFs, but be wary that more complex > statements still require MoreCommandsAsScript -- or > run them from a script.
Thanks, it sounds like there will be times MoreCommandsAsScript would be better. > >> However, I do find find it a little bothersome is how >> the pcf command list editor now splits the first line >> between commands and parameters (can't have >> everything). > > Me too. In the zip file that I uploaded you'll notice > that I simply didn't enter anything in the command > field. Just enter everything in the More commands box. > That's weird, when I imported the ini, it didn't end up that way. The first command block was used, and split across the parameter line as usual. Editing the actual ini, I see it was stored as Command 2 and Parameter 2 tho. Regards, Sheri Attention: PowerPro's Web site has moved: http://www.ppro.org Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/power-pro/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
