RPTools.net

Note that he said "free size", which applies only to Objects and Background images. And yes, those can be "freely resized" using the bottom-right corner's resizing handle.

Tokens and Hidden images can be set to "native size" and are not resizable (because their footprint is important, supposedly). Instead, the Config tab of the token editor can be used to resize the graphics image up to 2x without changing its footprint.


They should be. The campaign file version number did not increment in this release, so saving the campaign file will save it using the "1.3.b87" version number. (The version number of the file format is only supposed to update when an incompatible change is made. That didn't happen for b88.)

However, clients running a different version will not be able to connect. So all MapTool instances need to be b87 or b88, not a mix. (This doesn't apply to those running MapTool from Eclipse, since the "development" version has special code to allow connecting to any version for testing purposes. Be very careful with this if you're running MapTool from Eclipse because some things can get very weird if the individual instances don't match up. It's expected that this is okay for developers, since that's probably what they're testing. )

No surprise, I got the same "PaintChooser" error starting MapTool.
Windows 7 (32bits)
Java 1.6.0.29

Huh. That explanation makes it seem quite strange that loading the campaign up in b87 fixed the problem somehow ...

I tried changing them to background layer. Unlike Wolph, that didn't solve the issue. I don't remember if I tried changing them to Medium size then back to Freesize, though. I'll try that if it happens again ...

Thank you so much! Looking forward to use it!

I've some odd occurrences with b88 (and not b87).
- before (87) I was able to pull token images that now don't seem to show with no change to coding. I send tokenIDs and image assets through a macro.arg and it returns a broken image box-thingie.

- I get 'no Impersonated Token' error running macros that weren't there before (in 87).

I'm so confused!

I mentioned the broken image thing using input and label, is that what you're talking about? Need more info about impersonated token though. Also, if this is a part of using a framework, you should post the error there.

Oh wow, that's a bad bug. I dragged one rptok to map from library just fine, but ANY other rptok token I drag from library OR explorer just removes and duplicates the first one.

I played around with it a bit. If I create a new map I can drag tokens from explorer with no problem, but as soon as I drag a token from the library dragging from explorer no longer works for that map (corrupted). I can copy/paste from one map to the corrupted map, but dragging from the library or explorer still doesn't work for that map.

So, if you have a corrupted map you can create a new map, drag your tokens from explorer to new map then copy from new map to corrupted map. Copy/paste works on corrupted map.

Exporting map, deleting corrupted map and re-importing it does un-corrupt it allowing tokens to be dragged on from explorer.

This is only a bug for rptok tokens, not png or other images from explorer or library.

edit: b88 and b87 seem pretty compatible for saving and loading, so I've been doing my map editing in b87 but game playing in b88 because of the frame popup fix.

First of all, thanks Azhrei for the hard work put into this. I've been working on another project in RL and was glad to find that b88 has finally come out Being away has made me unfamiliar with some of the more salient points of MT; which brings me to my suggestion: I think it's best to create a batch file/process that runs the registry entries backup prior to running the provided .reg file that wipes everything clean. That or put some warning/instruction somewhere I guess instead of just an innocuous looking file

As everyone can guess, I fell right into the trap and wiped all my Global macros from the registry I made the added mistake of running b88 right after, thus losing all hope of key recovery

Sigh, that's what I get for not touching MT for 3 months and doing this at 3am in the morning Those were a lot of convenience macros lost XD. I just might crawl into a ball back in bed and weep

Anyway, if anyone should make the same mistake I did and ran the registry entries wipe by mistake, here's what you can try to do if, and only if, you didn't run MT right after (though it won't hurt to try):

1. Don't reboot/shutdown. If you're the cautious type, backup your registry and/or create a system restore point.
2. Download yaru, or some other utility that does the same thing. I use this since it's lightweight, has no dependencies and can parse registry hives for deleted entries
3. Opening the utility, you'll have to point out where you want it to look; in this case, you'll want to choose Open Software (local) under the File menue as the MT macros are found there.
4. With any luck, the tool will be able to parse the hive and display deleted entries which you'll find at the bottom of the tree to the left of the screen. Steps to export these entries as .reg files in order to re-inject them into the actual registry can be found online as I'm starting to nod off here As you might guess, since the registry is a volatile thing, putting off the recovery will likely spell failure for any future recovery attempt.
5. In the event of failure, you can try opening the actual registry (e.g through Window's regedit) and exporting the part of the registry that held the MT data as a hive file and have the tool comb through that. I'm pretty sure though that if the 1st 4 steps failed to yield results, the odds for success are pretty slim at best.

I'm still happy about the new release. Though the code I lost was significant and likely to put me off coding with MT while I deal with the shock, it was my fault in the first place I did notice that some of the bugs I submitted for a fix are still around, like radio buttons keeping focus instead of transferring it to the "Ok" button upon hitting the return key. Things look snappier though and I'll get to testing other stuff in the coming days to help out in the process

Thanks again for the hard work!

@Lee

If you want to recover those lost registry keys you can probably do it with your system restore. Here's what you can do.

• Run system restore and create a restore point for today.
  • Go to Start | All Programs | Accessories | System tools | System Restore
  • Create a Restore Point --> Next
  • Enter Restore Point Name --> Create
  • Go back to main menu --> Home
• Restore computer to earlier point
  
  • Restore my computer to an earlier time --> Next
  • Click calendar for most recent restore point before incident usually labelled "System Checkpoint" --> Next
  • Read Warning
  • After you've closed all the other programs click "Next" to restore and your computer will be restarted.
• Go to MapTool install directory and run "Backup MapTool Registry Entries.bat". This will create mtsave.reg with all your registry keys.
• You can either leave your system as is or undo last restore and run mtsave.reg. You can follow "Restore computer to earlier point" above and use your save point used in step 1.

This is the process done with Windows XP and other Window systems may have different ways of getting to the system restore (I'm not sure) and menus, but the process should basically be the same.

Well, there are numerous issues being reported, so don't thank me yet.


Heh, an "innocuous looking file" that's named Remove all MapTool Registery Entries.reg? Is it really that innocuous?!

But I suppose a bat file that runs the backup script first, then runs the .reg that removes them is a very reasonable idea! Regardless of what time in the morning you're running them...

I've been busy today folks, so I haven't poked into MT much today, but I'm going to look at it a bit right now and then will try to spend some time on it tomorrow during the day, if possible. Thanks for hanging in there!

Okay, I've now run in to the same problem. I haven't tested it fully to give my full review of problem, but it's on a campaign saved in b87 and then saved in b88. Those existing maps won't let me resize any images from the library or dropped from explorer. I can create a new map and resize an image and then copy/paste to corrupted map, but it will not allow resizing. I've also tried exporting and importing the map with no success. I can reload the map in b87 and have it work.

Okay, I've narrowed it down. New Campaign, drop token on background (resizable), drop token on token layer (background not resizable). New Campaign, drop token on token layer, drop token on background (not resizable).

So, once a token is dropped on to the token layer, no other tokens can be resized in b88.

edit: Actually, it's worse than that. As soon as a token is moved to the token layer images can not be resized. (ie dropped to background, changed to medium, changed to token layer. drop to background - no longer resizable)

@aliasmask Thanks for the tip, it was one of the first things I tried. This PC I'm using has an HD with very limited capacity, and since I've always been careful with my stuff (oh the irony), I disabled the automated recovery point creation years ago I do appreciate the help though

@Azhrei As I've said, it was a groggy early morning and while the file name did give me pause (like 2 seconds), I viewed what was in the file and said to myself when I saw the one-liner "Ah it's probably just references to what's in the appdata/etc folder, I could manually restore that later if ever..." It looked like a shiny red button so I pushed it and when I fired up MT and saw a blank Global, that was the only time I recalled that tidbit about MT storing Global in the registry I went from "Whoopiee, new MT." to "Uh-oh..." really quick after that

Good luck with sorting through the bugs. I'd just like to say what was improved were great improvements

With the resize bug and the 'if I drag a 2nd token to the map it's not placed but instead the first token is moved to that spot' bug. Should b88 not be marked as 'broken' as to me these seem rather severe bugs?

You're probably right, although I'll still use the broken one because it has a major fix in there for one of my players.

Not to mention the fact it doesn't even work at all for some of us.