isboxer error?

[Xixillia]

I was playing a bit before bed and realized that I needed to fix a keymap so I opened isboxer aaaannd

http://postimg.org/image/iuht4xrzn/


what did I do?

[MultiBear]

You played Horde. *dramatic, disappointed sigh*

Seriously though, I don't know what went wrong but fingers crossed your configuration file isn't corrupted!

[Ughmahedhurtz]

I was playing a bit before bed and realized that I needed to fix a keymap so I opened isboxer aaaannd

http://postimg.org/image/iuht4xrzn/


what did I do?

I get a TCP socket error when I open two instances of the toolkit (expected as the first instance already has the socket) but I don't recall seeing that specific error. I've never seen it do anything bad, but unless you're running two instances to compare profiles or copy things between profiles, there's really no need IMO. In fact, when I launch a second copy of the toolkit, I get a popup asking me if I'm really sure I wanna open a new copy.

[Lax]

Your issue is directly related to an input device plugged into your PC. Some devices end up corrupting the device name and it ends up breaking the XML after some time.

Send me the file InputDevices.XML in your Inner Space folder to lax@lavishsoft.com. I will use it to work around the problem so it won't happen again.

After sending me the file, make sure Inner Space is shut down and then delete the InputDevices.XML file from your Inner Space folder. Re-launch Inner Space, and it will re-generate. If I do not work around the issue for your affected device, then randomly in the future you will have the same issue again (assuming the same device is plugged in), and you can use the same solution.

[Xixillia]

Send me the file InputDevices.XML in your Inner Space folder to lax@lavishsoft.com. I will use it to work around the problem so it won't happen again.

Sent!

[Lax]

Thanks for sending that over, I've added the fix for this in Inner Space build 6109 which is now the development build of Inner Space.

I am working on some important (unrelated) fixes and am waiting on a confirmation on another fix, and then this build should go live soon.