Sat Nov 22, 2014 4:26 am
IsboxerToolkitGlobalSettings.XML ??
How does that settings file get its values?
I installed everything in a directory C:\Innerspace, not in the C:\program files (x86)\innerspace location which is apparently the default. It worked fine when I first set it up. I used ISBoxer to do the initial setup, creating some global character sets containing every character I might play, a single 9-window layout with all the characters from each account associated with one of the 9 windows, and a simple keymap defining several keys for controlling the boxed characters.
Once I got that working, I no longer had reason to load ISBoxer for normal play. I use AutoHotKey scripts rather than ISBoxer character sets to launch whatever particular configuration of characters I want to play at any given time, and just did not need the ISBoxer user interface any more.
(Of course, I am using ISBoxer under the covers to do the work: the AHK script issues commands like:
Run c:\innerspace\innerspace.exe run isboxer -launchslot m 1
WinWait is1
to launch slot 1 of global character set m on the current machine.
I prefix the run command with a "relay %computer%" if the character is to run on another machine.)
So, it has been months since I actually loaded ISBoxer, but yesterday I wanted to tweak the window layout a bit, and when I tried to export the changes to InnerSpace, I got errors saying it could not find various files in "program files (x86)\innerspace\..." locations. Which have never actually existed on my machine.
I could not find a user interface to tell ISBoxer where its files actually were. But I found the global settings XML and just manually edited it to point to the right place, and everything started working again.
I'm pretty sure that is not the intended way to manage the setup. How should I have fixed this problem? And can you tell me why the file got changed to those default locations?
I installed everything in a directory C:\Innerspace, not in the C:\program files (x86)\innerspace location which is apparently the default. It worked fine when I first set it up. I used ISBoxer to do the initial setup, creating some global character sets containing every character I might play, a single 9-window layout with all the characters from each account associated with one of the 9 windows, and a simple keymap defining several keys for controlling the boxed characters.
Once I got that working, I no longer had reason to load ISBoxer for normal play. I use AutoHotKey scripts rather than ISBoxer character sets to launch whatever particular configuration of characters I want to play at any given time, and just did not need the ISBoxer user interface any more.
(Of course, I am using ISBoxer under the covers to do the work: the AHK script issues commands like:
Run c:\innerspace\innerspace.exe run isboxer -launchslot m 1
WinWait is1
to launch slot 1 of global character set m on the current machine.
I prefix the run command with a "relay %computer%" if the character is to run on another machine.)
So, it has been months since I actually loaded ISBoxer, but yesterday I wanted to tweak the window layout a bit, and when I tried to export the changes to InnerSpace, I got errors saying it could not find various files in "program files (x86)\innerspace\..." locations. Which have never actually existed on my machine.
I could not find a user interface to tell ISBoxer where its files actually were. But I found the global settings XML and just manually edited it to point to the right place, and everything started working again.
I'm pretty sure that is not the intended way to manage the setup. How should I have fixed this problem? And can you tell me why the file got changed to those default locations?
