restricted > wanted to throw an idea of merging more than one of those items into a > single .ini. while maintaining:
An approach that would do something similar is to use a script of configure commands to do effectively merged importing. I know this means you still have to edit every file separately, but I am not sure that is a bad thing. >> -allow the more complicated scripts to be merged into a single ini I don't understand what you are getting at here. To me scripts and ini file are completely separate. Scripts are stored in text files. Ini files are used for storing configuration information on bars or buttons. ------------------------ 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/
