Zugg Software :: View topic

Posted: Sun Mar 30, 2008 10:35 am

In previous versions if I created a hotkey and pressed '5' on the keypad to the right it would put "KEY5" in the field. At the moment it puts '5' just like if I typed '5' from the number keys above the keyboard.

When I try to use a hotkey I manually set to 'KEY5' half the time it will take my override, the other half it seems to take the default settings set in the defaults packages.

Posted: Sun Mar 30, 2008 10:41 am

You need numlock to be... either on or off, I forget which. Whichever it isn't at the moment.

Wizard Joined: 25 Mar 2003 Posts: 1113 Location: USA

There is a problem with the KEY0 (Ins/0) and DEC (Del/.) macros, though, which I already reported. No matter which mode you're in, you can't get them properly defined in the GUI. Have to use the #KEY command to set them up.

Posted: Sun Mar 30, 2008 2:50 pm

No, turning the numlock off (it was on) gives 'CLEAR' as the value. Numlock on gives '5'. Neither of those are the 'KEY5' like defined in the default packages. Apart from that this isn't something I'm setting up for the first time. I've always overridden keypad5 even since Zmud days. It's just malfunctioning on Cmud for some reason. Some days I hit keypad 5 and it does my overridden function, other days it does the default function and ignores my override.

Posted: Sun Mar 30, 2008 4:42 pm

Hang on a second. What're you pressing to create the shortcut? When you create a macro with the package editor and you have the cursor in the key box, you need to press enter to bring up a dialogue to enter a key for the macro. You can't just press the button in that box and haven't been able to at all in CMUD. You're not doing that, are you?

Wizard Joined: 25 Mar 2003 Posts: 1113 Location: USA

Hey! You're right! Okay then. Could we please make that clear from the settings page when creating a macro? I didn't know that you had to use Enter to hit these keys, mostly because I've always created settings through commands and had less interaction with the editor than usual.

Posted: Sun Mar 30, 2008 6:06 pm

So does that mean that Key0 and del are working?

It does say in the tip at the bottom, but I agree that it's less than clear and suggested something similar a while ago. Guess we'll have to see.

Posted: Sun Mar 30, 2008 11:26 pm

Of the two items I mentioned, pressing the enter key fixes the first, but the second is still an issue:

1) Entering KEY5. I had no idea that this had changed since Zmud and I even had to go back into the program a second time and really search around to find the tip at the bottom of the screen. From a user interface point of view I don't think many people are going to clue in from that small tip at the bottom of the screen that only appears when you click in the box. Why not have a button next to the box where if you click it it brings up the box, or even just automatically bring up the box if you click in the field. Having used this in Zmud I had expected it to operate similar to Zmud.

2) KEY5 not overriding the default KEY5 which is set to 'look'. Apart from the above, it still only overrides the default value some of the time. Most of the time if I hit KEY5 it uses the default instead of my value.

Posted: Mon Mar 31, 2008 5:11 pm

This was changed on purpose from zMUD. When most people use an Edit Box in any windows application, then expect to be able to enter *text*. So, the key field in CMUD allows you to type the name of a key as a text value. Also, most people using an Edit Box expect stuff like Ctrl-C, Ctrl-V to activate Copy/Paste rather than putting the key into the field. So CMUD was changes so that the Key field works just like any other normal Edit Box in Windows. It is bad practice to change the keyboard behavior within an Edit box like zMUD did. That's why it was changed. I do not plan to change this back.

The tooltip in the status bar already tells you how you can press Enter to prompt for a key. People should be learning to read those tooltips for help since they often contain useful information.

For (2), I cannot reproduce any problem with this. When I'm playing Aardwolf, I have most of the keypad overridden by other macros and they never fail for me here, so it must be something specific to your package or window setup. Also remember that macros are specific to a particular window, so if you have clicked on a capture window, then the macros in your main session window are not going to work within the capture window.

Posted: Mon Mar 31, 2008 6:54 pm

i have (2) as a problem for me since 2.18

http://forums.zuggsoft.com/forums/viewtopic.php?t=29650

Wizard Joined: 25 Mar 2003 Posts: 1113 Location: USA

Maybe try and use the %priority function to see if you've got them out of order? I could see that your own macros might not override those in the default packages if your priorities got set lower.

Posted: Mon Mar 31, 2008 7:26 pm

You can always just remove the EnglishKeypad package to work around it.

Posted: Mon Mar 31, 2008 10:00 pm

Well, rather than working around the problem, I'd sure like to get a procedure to reproduce the problem to see if it's really a bug. I noticed that you never provided a procedure to reproduce the problem in the previous thread either. Which is why it didn't get fixed...if I can't reproduce something, then I can't fix it.

Posted: Mon Mar 31, 2008 10:04 pm

I'll try to see if I can accurately reproduce it. It doesn't malfunction 100% of the time, so it might or might not be possible.

Posted: Tue Apr 01, 2008 3:31 pm

I can't find a procedure to reproduce this. I see this happening in my main session file at times, and I can correct it by deleting the macro and creating it again, but in a blank session the macro always works 100%.

The best thing I can think of is to either send you my session or for you to tell me what other information I can gather when I see this occur.

Posted: Tue Apr 01, 2008 3:44 pm

I dont think it can be created in a blank session, as it will (or did for me originally) continue to work as expected until you next open the session.

But i can't seem to reproduce it in a temporary session either.

Posted: Tue Apr 01, 2008 3:46 pm

Posted: Tue Apr 01, 2008 3:50 pm

Posted: Tue Apr 01, 2008 3:50 pm

I was aware of the technique for doing it, if only because when i got an unexpected result i took a closer look and saw the directions.

Though I agree, I don't suppose you could do those tooltip bubbles (with an option to turn it off in prefs) that used to be so popular?

Posted: Tue Apr 01, 2008 5:32 pm

Posted: Tue Apr 01, 2008 11:40 pm

SubAdmin Joined: 18 Nov 2001 Posts: 5182

I have actually been trying to reproduce this since about 2.16. One portion of Toolbox uses a series of macros and at times since I made that portion they wouldn't work right. I have yet to figure out any possible combination to replicate it. Even with my main session where I am using it all the time I can't consistently replicate this.

I remember when I first noticed it, 5 of 11 macros worked. Next load 2 worked, but 2 that weren't working before, then seven, right now with 2.21 all 11 seem to be working correctly. For all I know 3 loads from now only 1 will be working.

Posted: Wed Apr 02, 2008 1:34 am

One thing you can try is typing #KEY on the command line to get a list of all enabled Macro keys. See if your's are in the list and enabled. You should see all current and inherited macros, so you should see *two* macros assigned to your NumPad keys. If a macro is disabled for any reason, there will be a "-" minus shown at the beginning. That might help determine if a macro is getting disable somehow.

Posted: Wed Apr 02, 2008 9:19 am

I must be doing something wrong. I type #KEY on the command line, hit enter, and nothing happens. Alternately perhaps something is happening, but the output is nothing. Are there any prerequisites I'm forgetting before I try this? I definitely have macros defined and I also have inherited ones as well, so this seems very odd. I can even use the macros and they function.

Posted: Wed Apr 02, 2008 4:55 pm

No, it should work. #KEY is a low level command for listing all enabled macros. It's similar to just typing #ALIAS to list your aliases, or #VAR to list your variables. If #KEY doesn't list anything and you still have macros defined, then there is definitely some bad problem with your settings or something.

1) Open CMUD, close the Session window
2) Press CTRL-K to define a key. Press a key, like F5
3) Enter "#SHOW fired" for the script and click the Save button
4) Type #KEY in the command line...it shows the F5 macro

If this doesn't work in a blank session, then something is definitely wrong.