I have some issues with the latest version of the game.
First of all, when I re-downloaded it and started to play again, I found that none of the keys that I had previously set did anything... in fact, no keys did anything, period. I figured out to open the Keyboard Settings open and started fiddling with that.
I went to set the arrow keys and found that when I tried to set the Move East option to the east arrow key, it gives me the message "no east" and refuses to let me set it to the east arrow key.
I also found it rather annoying that the key assignment popup would disappear behind the Keyboard Settings window if I accidentally clicked on the larger window instead. Would it be possible for these to both work from the same window to avoid this problem? I don't remember, but you might also be able to lock the Keyboard Settings window while the key selection is in progress to prevent this as well. In fact, you should lock the whole game window while in this editor, because I accidentally started my game while fiddling with the controls.
Also, the escape key should cancel the key selection. At least, that's what I'd expect it to do.
The controls started working again only after I finished up in the Keyboard Settings window. They should have worked as soon as I started the game. And I still can't set the East arrow key properly.
ID:287809
Jan 11 2010, 1:38 pm (Edited by moderator on Jan 11 2010, 2:02 pm)
|
|
One of the reasons I went with the text file approach was so that I could have multiple keys assigned to the same command. With the in-game macro editor approach this is impossible. It also makes the process of applying old preferences to the new system in a 1:1 way impossible.
I found a bug which could cause that, and have fixed it. Regressia was trying to load your settings on start-up, which can sometimes cause problems if timing is off and the client object hadn't been created yet. I moved the code to client.New(), so this should fix the issue. Please let me know if it persists.
Thank you for posting the actual error message, it lead me directly to the problem. This is fixed.
The problem is that individual controls can't have macro sets, only windows. How the editor should work is that you select an input control, hit a key, and then the code for that key is placed into the input. As far as I know this is impossible in BYOND. In order to allow for keys like Enter to be used, I have to capture the key myself using a separate window.
If there is a way to do this, I'm all ears. I tried setting "is-disabled" on the other windows, but this had no effect on selection and window "depth" order. I see no "lock" feature in the skin reference. Please let me know if you know of a way to do this.
That isn't working for you? The only problem I could find which would cause this would also cause another of those "No ESCAPE" messages... which might be pretty funny. Do you get a "No ESCAPE" or a "No ESC" message, or no message at all?
I've fixed everything that I think was leading to your problems. Would you mind testing an update for me before I make it public? If not, just send me a page.
Thanks