MapTool 1.3 Development Build 50
Moderators: dorpond, trevor, Azhrei, Craig
- trevor
- Codeum Arcanum (RPTools Founder)
- Posts: 11311
- Joined: Mon Jan 09, 2006 4:16 pm
- Location: Austin, Tx
- Contact:
MapTool 1.3 Development Build 50
The "Are we there yet" build
Build 50 (1/27/09)
* Optimize light rendering
* Update all JIDE libraries
* Remove auto-repaint thread
* Fix bug: memory leak in image token overlays
* Fix bug: Changing token or portrait image makes everyone else see a ? image
* Save docking layout persistence data to a specific file (makes for easier resetting)
* New Tool menu: Collect Performance Data, opens a window to gather data on map rendering, useful for debugging slow maps
* Add import/export of tables (Contributed by Applekor)
* Spanish translation update (Contributed by Patricio Acevedo)
* Support user preference to determine angles facing will use (point to cell edges, vertices, or both) (Contributed by Phergus)
* Windows .exe launcher (Contributed by Phergus)
* OSX launcher (Contributed by Azhrei)
* Fix bug: optional list delimiter in the FOREACH macro loop option (Contributed by Lindharin)
NOTES:
* I was not able to get azhrei's map import/export patched this build
* I was not able to get Gioppo's PCGen patch in
If you find specific bugs, post them in this thread or in the MapTool/Bug Report forum.
This build should fix several of the long running nasty bugs. Please keep an eye out for any oddities you come across and please post them.
The "Collect Performance Data" tool is something I put in to help you help me find the bottlenecks in the rendering code. If your map is drawing very slowly, turn on the collector tool for several seconds while you move/zoom the map (or whatever is going slow), then copy-paste the results from the window into an email and send it to [email protected]
There wasn't a full day of testing some of the patches, so if there's some critical bugs that sneak in, please make note.
Build 50 (1/27/09)
* Optimize light rendering
* Update all JIDE libraries
* Remove auto-repaint thread
* Fix bug: memory leak in image token overlays
* Fix bug: Changing token or portrait image makes everyone else see a ? image
* Save docking layout persistence data to a specific file (makes for easier resetting)
* New Tool menu: Collect Performance Data, opens a window to gather data on map rendering, useful for debugging slow maps
* Add import/export of tables (Contributed by Applekor)
* Spanish translation update (Contributed by Patricio Acevedo)
* Support user preference to determine angles facing will use (point to cell edges, vertices, or both) (Contributed by Phergus)
* Windows .exe launcher (Contributed by Phergus)
* OSX launcher (Contributed by Azhrei)
* Fix bug: optional list delimiter in the FOREACH macro loop option (Contributed by Lindharin)
NOTES:
* I was not able to get azhrei's map import/export patched this build
* I was not able to get Gioppo's PCGen patch in
If you find specific bugs, post them in this thread or in the MapTool/Bug Report forum.
This build should fix several of the long running nasty bugs. Please keep an eye out for any oddities you come across and please post them.
The "Collect Performance Data" tool is something I put in to help you help me find the bottlenecks in the rendering code. If your map is drawing very slowly, turn on the collector tool for several seconds while you move/zoom the map (or whatever is going slow), then copy-paste the results from the window into an email and send it to [email protected]
There wasn't a full day of testing some of the patches, so if there's some critical bugs that sneak in, please make note.
Dreaming of a 1.3 release
- trevor
- Codeum Arcanum (RPTools Founder)
- Posts: 11311
- Joined: Mon Jan 09, 2006 4:16 pm
- Location: Austin, Tx
- Contact:
Re: MapTool 1.3 Development Build 50
Couple more notes:
* I've changed the location of the saved window layout to make it easier to delete if things get really messed up, so your layout will revert to the default the first time you run it, you'll have to rearrange your layout.
* The new docking framework libs should fix many of the window problems we've had, please post if you are still experiencing them, or if you used to but are now working correctly
* Image zooming memory leaks should all be fixed now, please let me know if you find any more
* I've changed the location of the saved window layout to make it easier to delete if things get really messed up, so your layout will revert to the default the first time you run it, you'll have to rearrange your layout.
* The new docking framework libs should fix many of the window problems we've had, please post if you are still experiencing them, or if you used to but are now working correctly
* Image zooming memory leaks should all be fixed now, please let me know if you find any more
Dreaming of a 1.3 release
Re: MapTool 1.3 Development Build 50
I was playing around with the table import/export and it looks like after importing, the icons don't refresh. I have it stacked with the chat panel and if I switch to the chat panel and back, the icons show up.
Otherwise, it looks like it worked. Yay!
Edit: it also looks like it creates assets in XML. I'd much prefer that assets are saved as the actual image since that way I can preview it using GUI tools.
Otherwise, it looks like it worked. Yay!
Edit: it also looks like it creates assets in XML. I'd much prefer that assets are saved as the actual image since that way I can preview it using GUI tools.
- randyshipp
- Cave Troll
- Posts: 45
- Joined: Sun Jan 25, 2009 2:29 pm
Re: MapTool 1.3 Development Build 50
Is there any reason to suspect this will break Pyromancer's 4E Player Token macros?
Randy...
Randy...
Re: MapTool 1.3 Development Build 50
I don't think so. That is the next buildrandyshipp wrote:Is there any reason to suspect this will break Pyromancer's 4E Player Token macros?
Randy...
Seriously though, the only change I could see that may possibly do that is the foreach fix. But that is highly doubtful because if he was using that argument he would of run into the problem and reported it.
Re: MapTool 1.3 Development Build 50
Feel free to change it. This one was really just a quick feature I threw together without too much thought. Obviously, it needs to be changed anyway to fit into your unified import/export strategy.Azhrei wrote:I was playing around with the table import/export and it looks like after importing, the icons don't refresh. I have it stacked with the chat panel and if I switch to the chat panel and back, the icons show up.
Otherwise, it looks like it worked. Yay!
Edit: it also looks like it creates assets in XML. I'd much prefer that assets are saved as the actual image since that way I can preview it using GUI tools.
"Should" is the biggest word in the English language.
"Just" is the second biggest word in the English language.
What I'm working on
"Just" is the second biggest word in the English language.
What I'm working on
Re: MapTool 1.3 Development Build 50
In the default window layout, if you click on a folder in the resource library window, the contents of the folder is hidden by the Map explorer window. This will confuse new users when they can't figure out how to add images to the map.
Otherwise things are looking good. Thanks everyone for all the hard work on this.
Otherwise things are looking good. Thanks everyone for all the hard work on this.
- lmarkus001
- Great Wyrm
- Posts: 1867
- Joined: Sat Mar 29, 2008 12:30 am
- Location: Layfayette Hill, PA
Re: MapTool 1.3 Development Build 50
Once again, AWESOME JOB and thanks so much for everyone's hard work!!!trevor wrote: * Windows .exe launcher (Contributed by Phergus)
With the command line launch of MapTools we can configure the various memory allocations. How does the Windows .exe launcher figure into that?
Re: MapTool 1.3 Development Build 50
Azhrei,
For your Mac OS X Launcher, don't forget to strip those ^Ms...
cat LaunchMapTool-OSX.command | col -b > LaunchMapTool-OSXv2.command
...also, executing it from the Finder rather than the Terminal is returning:
Executing maptool*.jar ...
Unable to access jarfile maptool*.jar
For your Mac OS X Launcher, don't forget to strip those ^Ms...
cat LaunchMapTool-OSX.command | col -b > LaunchMapTool-OSXv2.command
...also, executing it from the Finder rather than the Terminal is returning:
Executing maptool*.jar ...
Unable to access jarfile maptool*.jar
Re: MapTool 1.3 Development Build 50
Try the Launch-MapTool.command in http://forums.rptools.net/viewtopic.php?p=80038#p80038 to see if you have any more luck.mezryn wrote:Azhrei,
For your Mac OS X Launcher, don't forget to strip those ^Ms...
cat LaunchMapTool-OSX.command | col -b > LaunchMapTool-OSXv2.command
...also, executing it from the Finder rather than the Terminal is returning:
Executing maptool*.jar ...
Unable to access jarfile maptool*.jar
Re: MapTool 1.3 Development Build 50
Yep, that one works - is it yours? If so, perhaps you can work with Azhrei in getting his to handle the bash variables properly for both Terminal and Finder execution If not, I can fix it if Azhrei needs a hand
Craig wrote:Try the Launch-MapTool.command in http://forums.rptools.net/viewtopic.php?p=80038#p80038 to see if you have any more luck.mezryn wrote:Azhrei,
For your Mac OS X Launcher, don't forget to strip those ^Ms...
cat LaunchMapTool-OSX.command | col -b > LaunchMapTool-OSXv2.command
...also, executing it from the Finder rather than the Terminal is returning:
Executing maptool*.jar ...
Unable to access jarfile maptool*.jar
Re: MapTool 1.3 Development Build 50
Heh, those are Trevor's ^M's! I sent him the file from my Mac so it only has newlines at the end of each line, no carriage-returns.mezryn wrote:Azhrei,
For your Mac OS X Launcher, don't forget to strip those ^Ms...
cat LaunchMapTool-OSX.command | col -b > LaunchMapTool-OSXv2.command
...also, executing it from the Finder rather than the Terminal is returning:
Executing maptool*.jar ...
Unable to access jarfile maptool*.jar
So, "Not my fault!"
- trevor
- Codeum Arcanum (RPTools Founder)
- Posts: 11311
- Joined: Mon Jan 09, 2006 4:16 pm
- Location: Austin, Tx
- Contact:
Re: MapTool 1.3 Development Build 50
I did a file->save as then committed it, so I never touched the fileAzhrei wrote:Heh, those are Trevor's ^M's! I sent him the file from my Mac so it only has newlines at the end of each line, no carriage-returns.mezryn wrote:Azhrei,
For your Mac OS X Launcher, don't forget to strip those ^Ms...
cat LaunchMapTool-OSX.command | col -b > LaunchMapTool-OSXv2.command
...also, executing it from the Finder rather than the Terminal is returning:
Executing maptool*.jar ...
Unable to access jarfile maptool*.jar
So, "Not my fault!"
Dreaming of a 1.3 release
Re: MapTool 1.3 Development Build 50
Hmm. Well, here's the first few lines from xxd:trevor wrote:I did a file->save as then committed it, so I never touched the fileAzhrei wrote:So, "Not my fault!"
Code: Select all
0000000: 2321 2f62 696e 2f62 6173 680a 0a56 4552 #!/bin/bash..VER
0000010: 533d 6d61 7074 6f6f 6c2a 2e6a 6172 0a4d S=maptool*.jar.M
0000020: 4158 4d45 4d53 5a3d 2237 3638 6d22 0909 AXMEMSZ="768m"..
Code: Select all
Content-Transfer-Encoding: 7bit
Content-Type: application/octet-stream;
x-unix-mode=0755;
name=LaunchMapTool.command
Content-Disposition: attachment;
filename=LaunchMapTool.command
Or maybe the SVN client did this? It probably defaults to the Windows version of "text" and adds carriage-returns to checked in files? Eclipse would hide that so it wouldn't be noticed.
And the Launch MapTool.sh script doesn't even have an EOL in it! (Which is bad, btw, as some shells won't execute a line without an EOL.)
Re: MapTool 1.3 Development Build 50
Basically you make a shortcut to it and you can add in the memory option there. I did a PDF for it that explains the process but I can't do attachments in the Announce forum and apparently we can't attach PDFs in any case. Sigh.lmarkus001 wrote:Once again, AWESOME JOB and thanks so much for everyone's hard work!!!trevor wrote: * Windows .exe launcher (Contributed by Phergus)
With the command line launch of MapTools we can configure the various memory allocations. How does the Windows .exe launcher figure into that?
I'll post the contents into a a post on the Developer Notes forum.
http://forums.rptools.net/viewtopic.php ... 226#p80226