Failure to Export to Innerspace

[Fippy]

OK Lax, I finally decided to take another look at ISBoxer. I ran the quick setup wizard, and went to export to IS..

File Not Found for Click Bar/Menu Image ... ISBoxer Images\Line Formation.png

[bob]

Your ISboxer images are not pointing to the installed location for some reason. Are you reusing an old installation that has moved locations?.

Also, it might help for you to check that the images exist where ISboxer thinks they should. If you select the Menus -> Toggles node in the top left pane, then in the lower left, select Images, and look at the default image set, each image will have a path. Verify they exist.

[Fippy]

Thanks for getting back to me Bob.

I have never had ISBoxer on this machine. I do have Innerspace, which I hope doesn't get fiddled with.

The images are in the InnerSpace/Scripts/ISBoxer Images folder.

Earlier I thought the message was in a couple of parts, but this may be one file:

File Not Found for Click Bar/Menu Image 'Line Formation pressed' : C:\Program Files(x86)\Innerspace\Scripts\ISBoxer Images\Line Formation.png

Under Images(global) and Image Set: Default, I see a list of images. Cutting and pasting from the first filename.

C:\Program Files (x86)\InnerSpace\Scripts\ISBoxer Images\Line Formation.png

But, clicking on browse next to the file: Brings up an explorer window in the Innerspace Folder, with "Line Formation".png in the filename. It is missing a couple of subfolders.

[lax]

Generally this should not happen as ISBoxer should be installed into the Inner Space folder. Did you install ISBoxer into a different folder?

[Fippy]

Ah. I moved Innerspace to another drive, so that I wouldn't need to mess with Windows' file protection. I'll go reinstall ISBoxer. It doesn't look like I need to uninstall it.
Thanks.

[Fippy]

Nope, still getting it. I installed to the D drive, and see that it wants to find images on the C drive.

PS: There isn't an InnerSpace folder in C:\Program Files (x86)

Edit: I just noticed that the Image Filename (for the file in the default image set) was a non-existant path on the C:
But when I click "browse" it drops me in the Innerspace directory on my D:

I suppose I could go through and move all of the images. But I probably won't.

[bob]

The file paths are hardcoded into ISBoxerToolkitGlobalSettings.XML file, and this is "normally" located in the same folder as the ISBoxerToolkit.exe (I'm sure this gets converted to something else as part of export too, but I haven't checked). If you move the Inner Space folder after installation (or you install ISBoxer separately to another location) then you may get some odd behaviour, although Lax will know the ins and outs.

I've had issues in he past using an old profile on a new installation when that installation is in a different location, but that has been more about missing image sets, and not due to the file paths.

[Fippy]

Innerspace was installed and then moved to the D drive. ISBoxer was then installed on the D drive, the Quick Setup Wizard ran, and an attempt to export. ISBoxer was never installed in another location. It was pointed at the same directory which contained Innerspace. And Innerspace was running fine out of that directory (although I don't think it stores paths).

There were no old profiles. This was the first time I have attempted to install ISBoxer on this machine.

I don't believe ISBoxerToolkitGlobalSettings.xml was on the system before the ISBoxer install, and nothing was moved during/after the ISBoxer install.

I have spent about 4 hours on this so far. This is exactly the type of thing which crops up each time I"ve tried (on other machines) to use ISBoxer.
I've seen the YouTube videos, that is not been my experience. And I'm tempted to just edit the paths by hand, but I have to wonder what else may be wrong out there.
Changing config files and having them in an inconsistent state could be worse than just doing nothing.

[lax]

The file paths are hardcoded into ISBoxerToolkitGlobalSettings.XML file

This is the opposite of being hard-coded... The file paths are generated based on the Inner Space install path, and then stored in the XML. I imagine there was a prior install or something to provide the C: value initially -- this is not something built into ISBoxer, there are no assumptions about your drive letters...

Anyway, I see that the real problem here is that there is code to automatically repair the filenames, but the formations "pressed" images are not automatically repaired. I've updated the code for next update to hopefully eliminate this issue in the future.

In the meantime you can just fix the path for the Line Formation pressed, Flying V Formation pressed, and 4 pt star Formation pressed images.

Innerspace was installed and then moved to the D drive. ISBoxer was then installed on the D drive

Okay that was the issue.

[Fippy]

Thanks Lax!

You mean IS saved pathnames somewhere? I was always rather nonchalant about moving the IS install out of C.

Anyhow, as I said, I don't mind changing the paths by hand. I just didn't want to make things worse without confirmation.