MapTool 1.2 Development Release Build 24

[trevor]

The "Tweaks, Bug Fixes, and Polish part Duex" release:

Build 24 (4/23/2007)
* Fix typo: Delete map confirmation, update "zone" to "map"
* Fix bug: revert last move was not updating vision
* Fix bug: hex facing angles
* Fix bug: hex grids were saving some cached information, which caused occasional problems when showing the grid the first time
* Remove hex grid aspect ratio code to allow non square hex grid tokens
* Add splash screen
* Add "http://portforward.com" to the Test Connection failure message
* Copy new tokens to clipboard so facilitate quick pasting
* Reassign "Load Campaign" shortcut key CTRL-O to "Show PC Token Vision Only"
* Never change a PC designated token's name on paste
* Make "Expose Visible Area Only" menu option always available

Keep banging away, not many trackers left for 1.2 !

[Emryys]

Keep banging away, not many trackers left for 1.2 !

Aye Captain...

[Phergus]

The "Tweaks, Bug Fixes, and Polish part Duex" release:

Build 24 (4/23/2007)
* Fix bug: hex facing angles

Uhm. Why did you change the facing? All the games that I am aware of face the hex sides, not the vertexes.

[Phergus]

The "Tweaks, Bug Fixes, and Polish part Duex" release:

Build 24 (4/23/2007)
* Fix typo: Delete map confirmation, update "zone" to "map"

Heh. When a map is hidden there is this big message up on screen saying that the "Zone" [is] not visible to players".

Map menu:

* "Hide from players" - Players should be capitalized.
* "Enable Fog-of-war" - War should be capitalized.

Or even better.

* Hide Map - to be consistent with the first two and make it shorter
* Enable FoW - to make it shorter

And then GIVE ME BACK MY &*#% SHORTCUTS.

[trevor]

The "Tweaks, Bug Fixes, and Polish part Duex" release:

Build 24 (4/23/2007)
* Fix bug: hex facing angles

Uhm. Why did you change the facing? All the games that I am aware of face the hex sides, not the vertexes.

Actually, the behavior that I saw pre-fix was that the tokens _were_ pointing at the vertexes and not the edges.

Aaah. I get it. The image I was using to indicate facing was tall, so when I used it to "point" it was off by 90degrees.

Hmmm. That brings up an interesting problem, how to handle tall, not wide, tokens.

In the mean time, I'll do another build tonight to swap back the angles.

[Phergus]

Aaah. I get it. The image I was using to indicate facing was tall, so when I used it to "point" it was off by 90degrees.

Hmmm. That brings up an interesting problem, how to handle tall, not wide, tokens.

Aren't non-square images supposed to default to top-down which should mean that they don't have a facing indicator?

In the mean time, I'll do another build tonight to swap back the angles.

And put the shortcuts back in?

[trevor]

Aren't non-square images supposed to default to top-down which should mean that they don't have a facing indicator?

It's not the shape of the image but the number of transparent pixels that determine the token type. The point is that the image was tall, not wide, so when I was looking at it rotated, the image was "pointing" to the angles and not the faces.

And put the shortcuts back in?

I get the impression this is important to you

[dorpond]

Issue and I think it is important:

When I change to Player View when I have Vision on a PC token, the token vanishes. I have no other player tokens on the map but a hundred or so monsters.

I loaded up 1.2B23 and it works fine.

Something broken with 1.2B24

[Phergus]

It's not the shape of the image but the number of transparent pixels that determine the token type. The point is that the image was tall, not wide, so when I was looking at it rotated, the image was "pointing" to the angles and not the faces.

Ahh. When I read you response it seemed like you were saying that the image wasn't rotating.

And put the shortcuts back in?

I get the impression this is important to you

Have I given that impression?

[trevor]

Issue and I think it is important:

When I change to Player View when I have Vision on a PC token, the token vanishes. I have no other player tokens on the map but a hundred or so monsters.

I loaded up 1.2B23 and it works fine.

Something broken with 1.2B24

Weird. Not sure what would have changed. I'll take a peek and include the fix in tonights build

[dorpond]

There is something seriously strange with Vision going on. My previous issue was when I loaded up older campaigns but even now when I create a new campaign file, I can only walk so far before my token vanishes. There seems to be an area and when I walk into that area, the token goes away.

To reproduce:
1. quickmap
2. enable FOW
3. Drop a token
4. add vision to the token -I used 40
5. Drop some NPC's and don't add vision to them.
6. Control I to clear that FOW from the player token.
7. Switch to player view.
8. Move the token around and do Control P to lift FOW in those areas.
9. Move the token around in areas that you previously remove FOW.

I am a Java 6 user so who knows. Again, this doesn't seem to happen with 1.2b23

[dorpond]

One request:
My campaigns are huge and often times span over months. This new Control O scares the living crap out of me. If you did the math of how many times I have to hit Control P throughout these massive campaigns, there is a really high chance that I will accidentally hit Control O instead of Control P and then all those months of revealed map is lost forever.

What am I to do if I accidentally hit Control O instead? There is no way for me to get my revealed map back unless I load up an old version of the campaign.

Can we make it not so spooky? A simple undo will be fine.

[trevor]

Can we make it not so spooky? A simple undo will be fine.

Hmmm, good point. Undo is going to take more work. I could move it to the other side of the keyboard until then ?

[trevor]

The vision stuff is my bad, some of my testing to figure out your other java 6 issue somehow made it into the source repo. I've fixed it and will make a build shortly

[dorpond]

Can we make it not so spooky? A simple undo will be fine.

Hmmm, good point. Undo is going to take more work. I could move it to the other side of the keyboard until then ?

That would be perfect.