wrote: > > Are you currently maintaining the single .pcf that gets replicated in > all locations (desktop, laptop, usb drive, work computer config etc)?
Yes, I have a single pcf that I use on multiple machines. Now, if your configuration changes wildly from one machine to another, somewhere you'll have to pay a price, either by having many .pcf files, or just one that loads a bunch of variations from text files/scripts. I don't think you can escape that. But you can organize it. I prefer changing text files to changing many pcf files. It takes less time, can be automated, and am better at it. > - Hotkeys (don't want to have to prefix each hotkey with a eg. if > (laptopvar) then run command else not). How to control to have them > enabled in 2 situations, but not the 3rd. Don't want to get into a > nightmare situation for testing multiple conditions for each hotkey on > triggering. The basic technique I use - and it can be applied in a lot of situations - is to check envvar COMPUTERNAME and load different configurations based on that. I do that in my startup.powerpro file loaded by a startup scheduler item. That implies that you have a smart startup.powerpro script... - Keyboard macros unique depending on the system. I don't have that, I wish I did. > - Media items - background, screensavers etc (I think these are read > from registry by powerpro at start, and not stored with .pcf so this > might be a non-issue) in my powerpro folder I have a _minimal_ media subfolder and carry it with me. powerpro is usually smart enough not to complain if it can't find a media file. > - Timers - some auto-start with some configs, not with others. Yes, > can make a single powerpro startup smart script that turns on the > timers you want...which might be the best idea. I don't use timers. > - Controlling GUI controls that are one thing with one device, and > another for another device (eg laptop and numlock shouldn't be locked > on - of course numlock lock doesn't work with XP ;P) I don't use many powerpro GUI controls - never had a need to customize from pc to pc > - Context menu's...I guess once you install on a system, it's enabled > for that system. Not installed in the registry, then it doesn't cause > a problem. It's easy to install -assuming sufficient rights- on a host system. Do it once and it will always be there for you. Then write portable context menu entries (I use my runit script...) - different Keytrap setups (this may be controllable with a > global startup script that renames plugin.ini files as-suitable) I do use keytrap but don't keep track of different keyboard layouts, etc. Too complicated. I prefer to use standard keys as much as possible, they're more portable. > - Startup items unique to the system...again probably a smart startup > script could control this, running commandlists as-appropriate per > config. yes > > ....any other items that I haven't thought of? In my powerpro folder I have a bin subfolder for those small utilities that I run again and again in combination with powerpro, and I like to carry with me. good luck! 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/
