KermitCrill: I just loaded 2.3.3 on Ubuntu Linux and it runs fine, at least, until I try to create a macro. As soon as I tell it to create a macro, and prepare to press the key I want to use as the Trigger, it acts like I've already pressed a key, and labels it with two carat marks, then asking me for the actual text of the macro. When I go back to the game, no keys work. Any idea what might cause this?

ReenenLaurie: I *think* it is so that when you press it while you are doing something else (such as viewing your inventory, or casting a spell etc.) to press Esc a couple of times beforehand to exit whatever you're doing. I know this was the behaviour of old, but I dunno how the latest macros work/look.

This is to prevent that if you accidentally hit the key while doing something else, you may be dropping your cool artifact sword, and so forth.

KermitCrill: I know that \e is supposed to be an Esc... but this doesn't appear to be an Esc (read again, it displays two carets which I can't type here because they create a superscript), and it happens immediately without me pressing a key, which means that I *can't* press the key I want to use as the trigger in time to get the game to use it. I either need to figure out how to keep the game from doing this, or learn how to manually edit the macros into the config files. Does anyone know why this is happening?

AnonymousHero: Are you using the X11/Xaw port by any chance? If so, you might check your Num Lock key...

KermitCrill: I *think* it's X11. The package in Synaptic does have dependencies of libx11-6 and libxaw7. But this appears to be happening regardless of the state of the Num-Lock. Then again, right now I'm connected via VNC, but that shouldn't affect it.

Ubuntu 2.3.3 - noobish macro problem (last edited 2007-04-24 16:37:21 by KermitCrill)