"[" broadcast key map

Hi all,

I'm playing Rift, and have a weird ISBoxer/InnerSpace issue. Specifically one key map does not work; the "[' key. Some details:

• Typing the "[" key map, seems to have no effect, but all other similar ones work fine (i.e. "p", and "]" are similiarly mapped)
• I have configured identical mappings with the wizard and without, at the same time, and separately with no problems for any other keys. e.g. I configure via key map wizard, multiple keys, and the [ key will not work, but others will
• Disabling the keymaps, and the [ key works fine in Rift; i.e on an individual box [ is ok, and all of them if I use repeater, [ is ok, but as soon as I turn on the key maps, [ key stops working
• I have deleted/recreated, saved/re-exported, exiting/restarted virtually everything, reordering keys, using different keymaps
• the [ key works fine outside of ISBoxer/Innerspace
• The .xml configuration for this key map shows no differences from other working ones. I.e. key [/code 26 seems virtually identical to key ]/code 27; I have a Logitech K350 keyboard if that is relevant, but guessing not

At this point, I'm guessing it's an ISBoxer/Innerspace issue. It's definitely related to ISBoxer/Innerspace, and definitely affecting my game play.

Any thoughts, help, etc. ? Forum search didn't show much specific to the [ key, but it's a difficult search query.

[bob]

Using [ as a hotkey does sometimes fail, although I have seen the odd config in which it was supposedly working.

My suspicion is that it confuses Lavishscript because [ is used as an opening bracket to denote indices, and unless it is correctly escaped, this is probably what it is interpreted as.

I could be wrong of course, but I do like to spread my theories around.

Using [ as a hotkey does sometimes fail, although I have seen the odd config in which it was supposedly working.

My suspicion is that it confuses Lavishscript because [ is used as an opening bracket to denote indices, and unless it is correctly escaped, this is probably what it is interpreted as.

I could be wrong of course, but I do like to spread my theories around.

Yeah, it seems like a valid possibility; I tried "xml escaping" it in a few of the fields, but that caused what looked like an XML parsing error, which is probably about the extent of my debugging. Regardless, thanks for the feedback, and if you're correct, guessing it will need to wait for a fix.

[lax]

I'll be issuing a fix for this soon, but it turns out the issue here is with [ in the Key Map or Mapped Key name itself, not the Hotkey or the key combo being sent. Changing the name of the Mapped Key to not include [ corrects the issue