I've checked in my updates. So everyone that has the source checked out, please do an update and try out the resulting MT.
Things to look at in particular were listed above in a previous post, but here's a recap: macros that use
Wiki: getPropertyNames() should be tested (I added a new macro, getPropertyNamesRaw but modified some shared code, so testing would be good), saving RPToks and loading them back into an older MT (since the assets will now be in binary), Test Connection now disables the UI while it's running, and the chat window should do a better job finding/creating links out of URLs.
Things that might break stuff: campaign properties now disallow names that differ only in case (so a property "ac" would generate an error when clicking
Update if another property named "AC" was in the property list), and lots of cleanup to parameter checking in macros related to token properties (functions such as
Wiki: getProperty() and similar). These changes are supposed to make it much easier to figure out why a macro doesn't work by providing better and more error messages (there's now three different error messages: not enough params, too many params, and wrong number of params).
Things to see if you like/dislike include the tooltips for all items on the Preferences dialog, and the new wording for "Auto-expose fog" (instead of "autoshow").
The items below are still on my hit list. I'd like to get them into SVN so that people can test them and if they seem to be working, then I'll do a b64. If it looks like I won't have time and the community tests of 5254 look good, I'll do b64 and plan on a b65 when I get these last few added.
- Figure out why single vs. double quotes matter when using <img src='asset://...'> inside a button label; see http://forums.rptools.net/viewtopic.php ... 30#p149609
- Add chat autosave support to MapTool
- Allow language translations to be external from the MapTool JAR file
- Save the view coordinates of each map so returning to a map restores those view settings.
- Add support for a set of global stylesheets?
I want those first two in particular (a bug fix and the chat autosave). I think bug fixes should have priority, followed by functionality that's already in the UI!
The last three would be "nice to have" features that I
will add, but they're not critical. It's a bummer about how translation updates happen now though, so I'm going to look at how the
ResourceBundles are defined. If I can add
.maptool/language (or similar) to the search path easily, then I want to get that in there sooner instead of later.
Separating them would let them update in parallel.
(look at the post time)
