--- In [EMAIL PROTECTED], Alan Martin <[EMAIL PROTECTED]> > P> Since the help file doesn't say, > > Yes it does. Near the top of the topic "Maintaining configuration > using .ini files" help says: > "Importing scheduled events or hot keys replaces[bold] any existing > scheduled events or hot keys which came from a Configure Import > and supplements[bold] any scheduled events or hot keys stored in > the .pcf file."
I saw that ( I did read the help, BTW ), but for some reason it was unclear to me if that meant that _matching_ hot keys would be replaced if they came from a config file, or _all_ hot keys would be replaced if they came from a config file regardless if of the contents of the config file being imported. Reading it again, I realize that I missed the key word _any_ in the sentence. > P> ... and I'm too lazy to check ... > > Fortunately most users are willing to check Help, else the list > would have a thousand questions per day. :-) Not checking the help isn't what I was referring to. I meant that I'm too lazy to 1) figure out the format of the ini file (I know, it's also in the help, but I haven't played with them yet) 2) come up with an example; and 3) test it when there was someone who had suggested it who might know the answer. If I had come across it on my own in the help and decided to use it, the story would have been different. I do read the help file, Alan, as the several message I've been sending with suggestions indicate. :p > P> or would I need to match the hot keys and just have them do nothing? > > No. Thanks for the answer. > By the way... > P> Each bar performs the same action, but with different values. > > Alternatively: > You could do that with only one bar which uses global variables > in its commands - and also in its button labels and/or tooltips > using *Info expr(variable). > A script which monitors the active window could import the > appropriate hotkeys ini file and change the variables used > in the single bar. > > Or, instead of using *Info labels, the single bar could use > the usual literal text labels and tooltips and make the script > change them with cl.SetLabel and cl.SetTooltip commands. hadn't thought of that. I'll have to put that on my list of things to try. Thanks, Paul ------------------------ Yahoo! Groups Sponsor --------------------~--> Make a clean sweep of pop-up ads. Yahoo! Companion Toolbar. Now with Pop-Up Blocker. Get it for free! http://us.click.yahoo.com/L5YrjA/eSIIAA/yQLSAA/JV_rlB/TM --------------------------------------------------------------------~-> 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/
