#9 setup.cmd makes a minimapexport.cmd

[cinderbdt]

The setup.cmd file in modpacker.zip makes a
minimapexport.cmd file. It also doesn't work, because
the command invokation inside the cmd doesn't have
nwn-io.jar in its classpath.

[Paul Speed]

Logged In: YES
user_id=652870

Hi. Thanks for the bug report. I think I may need a little
more information on the problem.

From a fresh install, the setup.cmd file looks like this:
@echo Creating MiniMapExport script.
@java -cp nwn-tools.jar org.progeeks.util.PathTool @java -cp
@cwd@\nwn-tools.jar;@cwd@\nwn-io.jar
org.progeeks.nwn.MiniMapExporter %%* > MiniMapExport.cmd
@echo Creating setpath script.
@java -cp nwn-tools.jar org.progeeks.util.PathTool set
PATH=%%PATH%%;@cwd@ > setpath.cmd
@echo Done.

Running the command generates a MinimapExport.cmd that looks
like the following (in my test environment):
@java -cp
C:\Temp\minimap-test\nwn-tools.jar;C:\Temp\minimap-test\nwn-io.jar
org.progeeks.nwn.MiniMapExporter %*

As you can see, both of these include the nwn-io.jar file.

Now, all that being said, if you were to unzip the
minimap-export.zip file into a directory with spaces this is
a known problem. The paths get messed up in this case and
the second jar file may not make it through. I need to fix
that bug.

So, if that's what the problem is here then I'll leave this
issue open as a reminder to fix it... maybe today if I have
time along with the other 32x32 image issue.

If it's something else wrong then we'll just continue
discussion to figure it out.

-Paul

[Paul Speed]

Logged In: YES
user_id=652870

Note: I just fixed the separately reported "Spaces in path"
bug:
http://sourceforge.net/tracker/index.php?func=detail&aid=1202065&group_id=80177&atid=558962

and that is now in version 1.0.0. So if this really was the
same issue let me know and I'll close it out.

Thanks
-Paul

[cinderbdt]

Logged In: YES
user_id=704004

The setup.cmd in the 1.0.0 version of modpacker.zip still
makes a minimapexport.cmd file, but minimap-exporter is a
separate download.

Here is what minimapexport.cmd looks like now if setup.cmd
in modpacker.zip makes it:
@java -cp "C:\Program Files\modpacker\nwn-tools.jar"
org.progeeks.nwn.MiniMapExporter %1 %2

In contrast, the minimap-export.zip file 1.0 has a setup.cmd
which makes a minimapexport.cmd that looks like this:

@java -cp "C:\Program
Files\minimap-export1-0\nwn-tools.jar;C:\Program
Files\minimap-export1-0\nwn-io.jar"
org.progeeks.nwn.MiniMapExporter %*

The setup.cmd file in the modpacker.zip file doesn't need to
have the line to create minimapexport.cmd in it at all,
because they are separate downloads. But, if you decide you
want to provide nwn-io.jar in the modpacker.zip
distribution, and edit the setup.cmd so that the
minimapexport.cmd gets created correctly with nwn-io.jar in
the classpath, then that would be another way to solve this.

Congrats on the 1.0 milestone!

[Paul Speed]

Logged In: YES
user_id=652870

Sorry for my immense density, I have trouble keeping these
tools straight sometimes. :)

I didn't realize you were talking about Modpacker generating
the file. Yes, this is a throwback to where the nwntools
had an all-inclusive zip... which may still be a good idea
but should be a separate thing. I try to keep download
sizes down so I don't think I want to include minimap export
by default.

I'll upload a bug-fix release later today. Thanks again for
your patience.