Error upon launching ISBoxer Suite

[lax]

Unfortunately, I'm now getting a fairly serious error that I don't recall having experienced before the patch. When using my hotkey (page up and down) to insta-swap between clients I now frequently (but not always) end up with stuck keys. I don't believe its a physical problem with the keyboard, since it seems to be coinciding with the most recent patch, and I'm not having any similar issues outside of ISBoxer. To be clear, I press Page Down and instaswap to a new client. That client thinks that my Ctrl key is being pressed. If I swap to a new window and immediately try to interact with it, I often experience serious issues as a result. Worse still, sometimes entire sets of windows think that their control keys are being depressed even when I'm not using them directly, and my broadcasted commands get completely fubared.

The issue is resolved by entering any client with the issue and pressing my Ctrl keys.

It's highly unlikely to be related to an IS patch; you can grab the previous version from the build archives to prove it: https://www.lavishsoft.com/innerspace/archives

Assuming I'm right and that it's not from the patch, we will need to figure out what is pressing Ctrl in all your windows, which should be in your ISBoxer configuration (unless it's you broadcasting the Ctrl key via Repeater and then aborting it somehow...). It would help to see your ISBoxer config; see the sticky "HOWTO: Share your configuration . . ." at the top of the forum for instructions

[Aerandria]

Unfortunately, I'm now getting a fairly serious error that I don't recall having experienced before the patch. When using my hotkey (page up and down) to insta-swap between clients I now frequently (but not always) end up with stuck keys. I don't believe its a physical problem with the keyboard, since it seems to be coinciding with the most recent patch, and I'm not having any similar issues outside of ISBoxer. To be clear, I press Page Down and instaswap to a new client. That client thinks that my Ctrl key is being pressed. If I swap to a new window and immediately try to interact with it, I often experience serious issues as a result. Worse still, sometimes entire sets of windows think that their control keys are being depressed even when I'm not using them directly, and my broadcasted commands get completely fubared.

The issue is resolved by entering any client with the issue and pressing my Ctrl keys.

It's highly unlikely to be related to an IS patch; you can grab the previous version from the build archives to prove it: https://www.lavishsoft.com/innerspace/archives

Assuming I'm right and that it's not from the patch, we will need to figure out what is pressing Ctrl in all your windows, which should be in your ISBoxer configuration (unless it's you broadcasting the Ctrl key via Repeater and then aborting it somehow...). It would help to see your ISBoxer config; see the sticky "HOWTO: Share your configuration . . ." at the top of the forum for instructions

The patch relation was just my assumption based on when the problem started, I'll assume I've just got some setting goofed up. I do broadcast the Ctrl key via repeater for targeting purposes, and its very useful in that function. Is doing so likely the root of my problem?

http://www.privatepaste.com/669382bd3c

the Full character set is the only one I use, the other is simply there from when I was messing around with how to use isboxer.

[lax]

I do broadcast the Ctrl key via repeater for targeting purposes, and its very useful in that function. Is doing so likely the root of my problem?

No, I don't think so.

However, the Ctrl+Shift+Alt+M and Ctrl+Shift+Alt+R Hotkeys that are used to adjust your Repeater Target might be involved in this issue.

Here's what I will guess is happening...
1. You are broadcasting, and start pressing Ctrl+Shift+Alt+M
2. Ctrl+Shift+Alt are being broadcast to the current Repeater Target, because it doesn't know you're using them for a Hotkey
3. The M gets eaten by the Hotkey, and your Repeater Target is changed
4. You let go of M and Ctrl+Shift+Alt. Ctrl+Shift+Alt releases get sent to your new Repeater Target; the previous Repeater Target doesn't get the memo to let go of Ctrl+Shift+Alt

Which means that a super simple solution for you, right now, may be to just change these two Hotkeys. And for me that I have a bug to work on.

[lax]

Okay I just issued a fix for the described issue, but as we're nearing the end of ISBoxer 41 Beta at the moment, the fix is in the beta.

You are welcome to participate in the beta and let me know if the new version solves the problem, with your existing Hotkeys. All you would have to do is install the new version (possibly back up your config first, to be safe), do a fresh Export to Inner Space, launch your team and try it out.

[Aerandria]

I do broadcast the Ctrl key via repeater for targeting purposes, and its very useful in that function. Is doing so likely the root of my problem?

No, I don't think so.

However, the Ctrl+Shift+Alt+M and Ctrl+Shift+Alt+R Hotkeys that are used to adjust your Repeater Target might be involved in this issue.

Here's what I will guess is happening...
1. You are broadcasting, and start pressing Ctrl+Shift+Alt+M
2. Ctrl+Shift+Alt are being broadcast to the current Repeater Target, because it doesn't know you're using them for a Hotkey
3. The M gets eaten by the Hotkey, and your Repeater Target is changed
4. You let go of M and Ctrl+Shift+Alt. Ctrl+Shift+Alt releases get sent to your new Repeater Target; the previous Repeater Target doesn't get the memo to let go of Ctrl+Shift+Alt

Which means that a super simple solution for you, right now, may be to just change these two Hotkeys. And for me that I have a bug to work on.

Got accepted into your beta group, will install that soon. Nonetheless, if it helps to understand the issue, I changed my Ctrl+Shift+Alt+R hotkey to the be only the ` button. Still having the problem, despite no longer using any Ctrl+ anything hotkeys.

Will let you know if I have any problems with the beta

[lax]

Fair enough, maybe I don't fully understand the issue yet; definitely let me know anything more you discover.

The scenario I described was definitely there though, and likely caused problems at least some of the time!