MapTool 1.4.4.0: Edit -> Preferences generates unexpected error

[jamztheman]

MapTool 1.4.4.0: Edit -> Preferences generates unexpected error

[dracwyrm]

Relavent info from gather debug information:

==== MapTool Information ====
MapTool Version: DEVELOPMENT
MapTool Home...: /home/user/.maptool
Max mem avail..: 3,556M
Max mem used...: 478,150,656M

==== Java Information ====
Java Vendor.: Oracle Corporation
Java Home...: /opt/oracle-jdk-bin-1.8.0.152/jre
Java Version: 1.8.0_152
Result of executing 'java -version':
............: Java(TM) SE Runtime Environment (build 1.8.0_152-b16)
............: Java HotSpot(TM) 64-Bit Server VM (build 25.152-b16, mixed mode)


==== OS Information ====
OS Name........: Linux
OS Version.....: 4.13.7-gentoo
OS Architecture: amd64
PATH...........: /usr/x86_64-pc-linux-gnu/gcc-bin/7.2.0:/usr/x86_64-pc-linux-gnu/aarch64-unknown-linux-gnu/gcc-bin/6.4.0:/usr/local/bin:/usr/bin:/bin:/opt/bin:/usr/games/bin
Number of Procs: 12

[JamzTheMan]

I now store some preferences (JVM parameters) using the packager class (this is so the native executable can access them before launching the jar).

To run it manually you need the dll/so lib for your OS and add a -Djava.library.path={path} to those files. I've included windows/linux versions here: https://github.com/JamzTheMan/maptool/tree/1.4.4.0/lib

Alternatively, you can simply run the command gradle run which defaults the needed args/jvm options for you in a fresh checkout from github.

Or, you can also run the command gradle deploy which will create a native installer for you and you can install it as normal. (you'll find them in your releases\release-{version}\bundles dir)

I'll close this issue as this is intended behavior, but feel free to reopen if you have further issues.

[dracwyrm]

doing ./gradlew deploy yields this:

:deploy FAILED
:deploy (Thread[Task worker for ':',5,main]) completed. Took 0.004 secs.

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':deploy'.
> A problem occurred starting process 'command 'javapackager''

Also, when I try ./gradlew run, the settings for stack, min and max heap sizes don't save.

[dracwyrm]

I start MapTools with the script in the bin dir via ./bin/MapTools. It loads and the Preferences Dialog box now opens with your libpackages.so file (is it 32 or 64 bit?).

However, when I enter a value for stack, 128M, the value is saved but it's not used when MT starts. I opened a campaign that made on a previous version that uses Bag of tricks for doors that toggles and Fog of War. No matter what I put in the stack size box, I get the error when trying to toggle the door that I ran out of stack space and that I should increase it.

When I add these arguments to the start options in the script, "-Xms512M" "-Xmx2560M" "-Xss128M", everything works. No longer a stack size error. Why isn't the values being used on start up?

[JamzTheMan]

The values are only used if you start from the installed version. The native executable is launching the jvm and using those values. If you launched manually for testing you have to user your own values as you did...

As for deploy, what OS? Search for javapackager as part of Java and it will tell you what you need. I only package for x64 so there libs I provide are for x64.

You also should have Java 1.8 installed to create deploy (151 is latest)

[dracwyrm]

I use Gentoo Linux. Apparently, they forgot to link in javapackage in /usr/bin. All java files are in a different directory, so I symlinked to /opt/oracle-jdk-bin-1.8.0.152/bin/javapackager and it appears to build.

It created a RPM (is there a way to have it do a tar.gz version that can be extracted?), which I had to extract, but I was able to run it. However, is the text for the tokens on the left side being weird and overlapping normal? https://imgur.com/a/ruYza

Thanks for your help. :)

[JamzTheMan]

I've only tested ubuntu and Deb disto. But I went core Java this time so less shenanigans than with jwrapper.

It does also just create a unified jar as well. I will need to put a try catch in the and disable the jvm prefs though if people plan to run without the installed version...

Re the text, no, I've never seen that before. It just uses a system font and nothing special.

[dracwyrm]

Thanks for all your help. I got the launcher working fine with Gentoo, so that's one more tested platform. The RPM needs to be manually extracted and the files copied to the right folder. The desktop file goes to a different location as well. Nothing an ebuild can't fix.

The new launcher works a heck of a lot better than JWrapper. I had nothing but issues with it on Gentoo and the constant fighting.