> I have posted a beta of the configuration program pproconf.exe at > http://www.windowspowerpro.com/download/TextConfig.zip
Preliminary testing with hotkeys and schedulers for different options I tried testing with, it was working flawlessly. Commandlists, just couple items so far: 1) Commandlist items with "own background" and "own text color". These properties are saved with the export, but not imported in. 1a) CommandList Items: If you have a tooltip text when it exports, it appends an "=" onto the beginning of the field. 2) With command list properties dialog fully filled with this: [Properties] Name = _Bar: !Main FontName = FontInfo = BackBMP = background Format1 = IconSize: 16 Position: Floating SlideFrom: FromRight Format2 = HideAfter: 250 Height: 10 MaxText: 100 Transparent: 10 Gradient: 10 Format3 = Flat Back: 0 0 0 Text: 0 0 0 TextUnder TopMost SameSize Vertical Border Tooltips AllVDesks 3DFrame Format4 = TextCenter BarSize BumpWithin Marker RightIcon NoFlicker HoverClick TextRotate TextVertical MenuIconSmall ToolTipsMenuText MenuNoMaxText Folder = testinexportunderfolderbutontab FolderMenu = folderdots folderstart nofolders mne noext folderback nofiles explorer noicons embed nohidden foldershortcut foldertop back *all nosubmenu tooltips Autocolall 10 button sortext Maxtext 10 depth 10 .txt cmd "command" zero "vartozero" fileman "nameforexplorer" Exclude "excludefolders" FolderFormat = AutoRefresh ShowText SortExt IncludeHidden Explorer2 NoLnk NoExt UseLast It finds one error on the "FolderMenu" import (watch for word wrap). Once that error is fixed, it should import with every checkbox checked and field filled under the menu format dialog. All dropdowns changed from default, any number fields changed from default. 3) On the export, if you use the same name of an existing file, there is no "Are you sure you want to replace that file" confirmation. Not sure how important this is though. 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? Does the /* */ commenting available break standard ini parsers? Haven't tested that, haven't worked with ini parsers enough...yet ;) That's all for now, looks great! =) ------------ Anyone have ideas on how you'd manage scripting the merging of commandlists/hotkeys/etc? I believe this wasn't going to be an addition that Bruce was adding. If it isn't added, I'll probably be trying to make something that will let you do that, if I can figure a relatively simple implementation technique. Ideas? David Troesch | Atlanta, GA | ICQ# 2333123 Those who would give up their liberty for security deserve neither. Funstuff: If I save time, when do I get it back ? ------------------------ 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/
