Zugg Software :: View topic - Package Editor prevents function key macros from working

Posted: Sun Dec 07, 2008 7:50 pm

It seems that the package editor uses the F3-F12 function keys to control the display of the various classes of items in the package editor. I have macros that make use of some of these function keys. The macro keys work fine if the package editor is closed, but if the package editor is open (but in the background) it still consumes the key presses and doesn't allow the macros to fire. Is there any way to prevent this from occurring other than always closing the package editor window?

It probably won't be an issue I notice once I have everything converted from zMUD and working correctly, but its nice to be able to leave the package editor open so I can make quick changes to things that are not working. No biggie if there is no workaround, it might be nice if it was noted somewhere though since it is not at all obvious why some of your macros just suddenly stop working :).

Wizard Joined: 26 Mar 2008 Posts: 1547

Options -> General -> User Interface -> Command Tab

Checkbox that says "allow any key to be a macro"

Posted: Mon Dec 08, 2008 1:24 am

I tried that just to be sure and confirmed it doesn't fix the issue. The problem isn't that you can't create the macro for the function key, you just can't use it while the package editor is open in the background.

Magician Joined: 28 Jan 2007 Posts: 430

Well, I just tried it on an Untitled session and it works for me.

What I did was,

Hit ESC to get Untitled

Create a macro, naming it F3

Minimizing the Package Editor window (is that what you mean by background?)

Pressing F3 repeatedly while Main Window had focus.

Everything worked just fine. Macro had the value of "#say blah.", and by pressing it, it works each time,
sending "blah." to the screen.

Posted: Mon Dec 08, 2008 2:46 am

Yeah, thats exactly what I mean by background... either minimized or just leave it maximized but click on the main MUD window to give it focus. Either way my macros for F3-F12 stop working.

Maybe there is some setting somewhere causing it that I'm not seeing or something. Not a huge deal anyway now that I know (or at least think I know :) what is causing it. Was just frustrating not being able to figure out why my macros kept on working and then not working over the first few days I was using cMUD.

Thanks for all the help.

Posted: Mon Dec 08, 2008 6:13 pm

Sorry, but whatever window has the keyboard focus is always going to take the function keys. If the Package Editor has the focus, then the function keys are used for the editor and your macros will be ignored. This is a Windows issue...Windows always passes keypresses to whatever window has the focus. As mentioned, you need to minimize the package editor, or just click on your main MUD window to give it the keyboard focus again.

If you are trying to CREATE a macro for the F keys, then when you are in the macro Key Name field, look at the help message in the status bar at the bottom of the window and you'll notice that it says to "Press Enter to select a key" for the macro. You can manually type the string "F5" or you can press Enter and then press the F5 key.

Posted: Mon Dec 08, 2008 6:33 pm

I am not trying to create the macro, I saw that status bar message you referred to and successfully created the macro just fine.

I also have clicked the main MUD window as well as minimized it, neither one works. Maybe there is something else in play here, but as soon as I physically close the package editor window instead of minimizing it, my macros work fine again, every time. The F1 and F2 keys are never affected in this manner, which is why I associated the problem as being the package editor consuming the F3-F12 key presses even though that window doesn't have the focus. Maybe it's something weird with my laptop or Vista, I don't know.

I'll just keep the package editor closed while playing, no biggie since apparently no one else has this problem anyway.

Posted: Mon Dec 08, 2008 6:52 pm

Which version of CMUD, and which of windows? I don't see this on XP with 2.37.

Posted: Mon Dec 08, 2008 7:01 pm

It is the 2.37 version of CMUD on Windows Vista Business edition Service Pack 1.

Posted: Mon Dec 08, 2008 8:35 pm

Not sure what the problem is. On my Vista system here, I can leave the package editor open and then just click on the command line and press my F5 macro and it works just fine. Doesn't matter if I minimize the editor or not. Just clicking on the command line in the main MUD window (or clicking on the main MUD window itself) and then pressing my macro works.

Sounds like something is giving the keyboard focus back to your package editor window. Are you running any Windows enhancements that might be messing with the normal behavior of Windows?

Posted: Mon Dec 08, 2008 10:03 pm

You're definitely right about it behaving as if the focus is being given back to the package editor window. To test it I opened the package editor window and had it set to view all settings. I then minimized the package editor window and gave focus back to the main MUD window. When I use F5 and then go look at the package editor window again, the view has changed to show only aliases. Likewise, with F3 the view has changed to not show classes.

I don't have anything special as far as enhancements or other programs running that I know of... I stopped a couple of programs like powerstrip that lets me do custom monitor resolutions and google desktop just in case, but that didn't fix it. I have configured Vista to Classic mode since I hate all the new crap that made it different from XP if that makes a difference.

I'll go through my process list and see if I can find anything suspicious that could possibly cause this since it appears to be something particular to my setup and update this thread if I can find anything.

Thanks for all the help.

Posted: Wed Dec 10, 2008 3:44 pm

I've tried to figure out what is going on with this without any luck. I installed on one of my other computers and it works fine there just like it is for everyone else. I tried playing around with some of the settings in Vista, getting rid of some programs I didn't need, and stopping some services that seemed like they could have been related, but no luck. Guess it's time to get a new laptop since this one isn't in very good shape anymore anyway.