Build 16: Alt-tab bug fixed

[Fursphere]

Great.


Like Zenga says, let's get rich!

Deal!

Let me try to remember recent requests.

The next thing on your list was keymaps. I think the next thing on Moorea's list was no-pass. That's sort of the same, right?

I might have to do "launch WoW" before keymaps make much sense.

Actually yes, the "Launch WoW' feature would be really really cool.

Do not pass lista and keymaps are similar - but still different.

Do not pass has been described as a "white" and "black" list as well. THe most often used feature of this is for movement keys. WASD. So on the "boardcasting" mojo (current focus or main) - all keys would be broadcast (white list keys) EXCEPT "WASD" (blacklist). Its basically a list of keys you would tells mojo to "not boardcast".

The benefit here is you don't have to redo keybindings within WoW. And if you make a new WoW your "focus" or "main" - your movement keys are already setup - no rebinding. A seamless transfer.

Keymaps are changing the logical mapping of keys from one mojo to the next (or wow to wow on same pc setups).

Example:

WoW1 = A is pressed
WoW2 = A is mapped to B
WoW3 = A is mapped to C
WoW4 = A is mapped to D

So when you press A on the main, B, C, or D gets pressed on "alt" WoW's depending on there individual keymappings. I personally don't like this concept - but a lot of others have come to love it with the other broadcasting soloutions.

Other people asked for visible cursors, status overlays, um, what else.

Edit: mouse broadcast.

I don't think you've even written the code for mouse broadcasting yet? I'm not sure how many people actually use this on a day ot day basis vs. a "neat toy to have" feature. Would be interesting to find out.

Edit: Set a PC not to receive incoming (as opposed to the existing mode buttons and hotkeys which all affect outgoing).

Edit: re-enable WoW window and finish the code that tracks scheduled and running WoWs.

This is going to be very handy for multi-client users (more than one WoW per PC). It looks like you're half way there with the new "WoWs" button info.

Edit: Triggers need to be finished. They don't yet include an option for "trigger when key is released" and "allow or disallow typematic presses to trigger this hotkey."

You can currently do creative binding IN GAME to do "on release" stuff. How many people actually use it? Not many I would suspect. I really don't know a practical use for binding "on press" vs "on release"

Edit: There are two remaining bugs on the bug list but I'm inclined to leave them for now since they will be a pain in the ass and nobody has complained about them.

Oh? I haven't notice them yet. What are they?

Moorea, if you're reading this, you know what would help me in the FAQ? If you could figure out some way to include a running summary of requests with a count of how many people asked for each one. A top-ten requests list. Right near the beginning of the FAQ.

I was considering doing this myself. Let me talk to Svper and see if I can get some mod access to clean things up a little on this forum.

Does the word "keymap" come from Keyclone? Can someone post a screenshot of what a keymap config screen looks like so I have a better idea of what's being requested?

I dont' know where the term came from. As far as a UI goes... hmm.... with the amount of keys available on a keyboard, the UI could get HUGE. I'm almost thinking some sort of spreadsheet type layout with a list of "input key" in one column, then multiple "output" columns on a per WoW basis (multi PC aware). So you can just type in what key you want output based on the input key.

Maybe even a dynamic hotkey system like you do in the other menus - that add boxes as you use them?

[Freddie]

Example:

WoW1 = A is pressed
WoW2 = A is mapped to B
WoW3 = A is mapped to C
WoW4 = A is mapped to D

So when you press A on the main, B, C, or D gets pressed on "alt" WoW's depending on there individual keymappings. I personally don't like this concept - but a lot of others have come to love it with the other broadcasting soloutions.

I think the program should do that. I think also that this sort of setting should nest. I.e., a single setting of this type for all WoWs. Then individual settings for individual WoWs that might override only a few keys. (I think all config info in the program should work that way.)

I don't think you've even written the code for mouse broadcasting yet? I'm not sure how many people actually use this on a day ot day basis vs. a "neat toy to have" feature. Would be interesting to find out.

I haven't written it yet but I've written this kind of code before in HotkeyNet.

This is going to be very handy for multi-client users (more than one WoW per PC). It looks like you're half way there with the new "WoWs" button info.

Unfortunately I just decided to rewrite the code that underlies that button. The xml file for config info, the data structures that represent WoWs and all other config'd objects -- out it goes. I've been having a lot of trouble getting it designed in a way that will make the rest of the program easy to write (it has to support the nesting stuff above and some other operations).

(Continued in another post)

[Freddie]

You can currently do creative binding IN GAME to do "on release" stuff. How many people actually use it? Not many I would suspect. I really don't know a practical use for binding "on press" vs "on release"

It's necessary for some very simple things in the script language. For example, making a hotkey that causes movement in a game. I won't work on the script language for a while, but the trigger code I wrote last week is the same code that will be used for the script language.

Oh? I haven't notice them yet. What are they?

Actually there are three known bugs now. Somebody told me one last night in a game.

1. When you close a Mojo, a connected Mojo may not close both its socket connections. Then when you reopen the closed one, the connection may not get fully reestablished.

2. If you close a Mojo whlie moused over, one or both cursors may get disabled or trapped.

3. Last night somebody reported that remote mouseover cursor gets trapped in a window belonging to Dark Age of Camelot.

I was considering doing this myself. Let me talk to Svper and see if I can get some mod access to clean things up a little on this forum.

Omg you're going to mod again!

I dont' know where the term came from. As far as a UI goes... hmm.... with the amount of keys available on a keyboard, the UI could get HUGE. I'm almost thinking some sort of spreadsheet type layout with a list of "input key" in one column, then multiple "output" columns on a per WoW basis (multi PC aware). So you can just type in what key you want output based on the input key.

That's kinda what I was thinking too. Except with the nesting idea maybe the entries should be color coded to show whether they are inherited (defined in a parent setting) or overriden in the current setting. And maybe there should be tabs to look back at parents from which the current settings are inherited.

And then I think -- this is too complicated for Mojo.

I never counted but the OS probably defines something like 150 or 200 key codes.. In addition some hardware devices (by mistake) use non-existent key codes so in a way there are 512 because the codes are defined by nine bits.

Maybe even a dynamic hotkey system like you do in the other menus - that add boxes as you use them?

We can draw the boundary between "broadcast" and "hotkeys" anywhere we like.

Broadcast is just a subset of hotkeys, and it can include as much hotkey stuff as we want.

I'm thinking that the input to broadcast (the trigger) should always be a single key press or release. Whether the output can be a combination... I dunno, that's something to decide.

Certainly, the program will be able to do that, but I dunno which part of the program should do that ... which screen the user does it on, whether it's called broadcast or something else.