> Thanks for your help and I will fix the bugs you have found.
> On import and export, I see that the exporting of all commandlists > capabilities have been removed. I understand that you're keeping one > commandlist per .ini file. Is the option of making the export routine > capable in the future of exporting multiple items (to different .ini files) > a planned addition in the future? I implemented this stuff for people interested in maintaining configurations in text files. So my understanding is that both the import and export to functions of configuration program won't be used that much -- what will be used is the direct import to PowerPro (which will reuse the some import code form config program). So I don't plan enhancements in the export area. >> ------------ > Anyone have ideas on how you'd manage scripting the merging of > commandlists/hotkeys/etc? I will be implementing conditional of form ;if (expression) stuff ;else other stuff ;endif where expression will be evaluated by PowerPro (which must be running). You can use this with include statements to mash together various hot key files or event files or command list files into a single virtual input file (of any one type). ------------------------ Yahoo! Groups Sponsor ---------------------~--> Buy Ink Cartridges or Refill Kits for your HP, Epson, Canon or Lexmark Printer at MyInks.com. Free s/h on orders $50 or more to the US & Canada. http://www.c1tracking.com/l.asp?cid=5511 http://us.click.yahoo.com/mOAaAA/3exGAA/qnsNAA/JV_rlB/TM ---------------------------------------------------------------------~-> **** EDIT YOUR POSTINGS !!!! **** Please remove as much as possible from original messages before replying to them. ________________________________________________ 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/
