MapTool 1.2 Development Release Build 7

Post by **trevor** » Tue Jan 30, 2007 1:39 am

This build specifically fixes several issues that were introduced in build 6. Please let me know if you are still having issues with the fog. It also picked up some features that were contributed since build 6:

Build 7 (1/30/2007)
* MRU list (contributed by galneweinhaw)
* CTRL-X to cut tokens, and associated Edit menu item (contributed by galneweinhaw)
* Bug fix: token sequential naming (contributed by galneweinhaw)
* Token sequential numbering naming tweaks (contributed by galneweinhaw)
* Add CTRL and SHIFT modifiers as F key modifiers for macros (contributed by galneweinhaw)
* Fix F10 key issue (contributed by galneweinhaw)
* Preference panel UI layout updates (contributed by galneweinhaw)
* Bug fix: tokens disappearing in player view
* Bug fix: update server state when updating token vision
* Bug fix: token vision shape not updating when rotating token
* Prefix all rolls with "*" to prevent cheating
* Macro button label updates
* Vision objects are now nameable
* In the vision menu list, left click to toggle enabled state, right click to edit

NOTE: This does not address the texture shapes lining up, that will be addressed in build 8

Post by **trevor** » Tue Jan 30, 2007 1:45 am

Heh, let the bugs begin:

Snikle notes that the menu option for expose last path doesn't work. On inspection, that makes sense since I moved some code and forgot to link it back up

On the positive side, the shortcut key works. I've fixed this and it will be in build 8

thelevitator · Post by **thelevitator** » Tue Jan 30, 2007 1:49 am

How do you set the expose so that it only shows the immediately visible area? The visible area lights up, but the fog doesn't seem to recover the area that the token has moved out of. I'm still trying to keep up with all the advancements, so let me know if that's currently not available.

Post by **trevor** » Tue Jan 30, 2007 1:52 am

Yeah, there's a menu option for that, but it only works when you are running a server in strict token management mode, and you right click on a player owned token. You'll get an expose option for Player View Only

Post by **trevor** » Tue Jan 30, 2007 2:05 am

Snikle reported that stamps are disappearing when outside of your token's vision.

That's a bug. It's been fixed for b8 (which will probably be released on Thursday, give you guys a chance to find any other bugs that I've missed)

snikle · Post by **snikle** » Tue Jan 30, 2007 2:13 am

wooohoo! Look at that, got the first bugs reported baby!

Post by **dorpond** » Tue Jan 30, 2007 8:14 am

Definately better with the token disappearing issue that we reported in 1.2B6.

There is still a slight issue with it though - more of a measuring issue than anything else.

In this example, you see no token because it is out of vision. this is expected behavior:

But when I move up my token up one square, the other token becomes visible, even though it isn't in the vision. This is probably due to the blocky light vs. the rounded:

Post by **trevor** » Tue Jan 30, 2007 8:17 am

Actually, it's probably because of a single pixel overlap. The block cell is probably one pixel offset, which makes it overlap the cell with the token by juuuuust enough to make the cell visible. You only need a single pixel overlapping the rectangle that surrounds the token in order for it to be considered visible. We need to figure out how we want to handle precision edge cases like this

torstan · Post by **torstan** » Tue Jan 30, 2007 8:43 am

I noticed a similar effect in the test I used. I'm using the non-blocky vision and if the slightest edge of a square is in the visible area, any token in it is visible. This seems a little odd.

I'd like it if players could only see the bits of tokens that lie in the visible region (the lighter area in Dorpond's example). So players generally only see bits of tokens (for non-blocky light) or whole tokens in squares they can see (for blocky light) when a token is on the edge of their vision.

I'm sure that other people will have a different preference.

If players could only see bits of tokens then it would be possible to really freak them out too (I see a tail! What of? Don't know, but it's big...) - which is never a bad thing.

Otherwise, it's looking great. No problems so far and a map that is unusable before (4 tokens with 60ft vision) now ticks over nicely at ~8% CPU or ~15-20% when a token is moved. Whatever optimisation has gone in has made a big improvement.

Phergus · Post by **Phergus** » Tue Jan 30, 2007 10:01 am

The outline marker for conic vision isn't rotating with the token until after a movement has been performed.

Also there is some debug output printing the name of the Vision.

Post by **trevor** » Tue Jan 30, 2007 10:31 am

Phergus wrote:The outline marker for conic vision isn't rotating with the token until after a movement has been performed.

Also there is some debug output printing the name of the Vision.

Interesting. I specifically checked this right before building. Could you give me your specific repro steps, perhaps I missed a case.

Post by **dorpond** » Tue Jan 30, 2007 10:47 am

It seems to work fine for me. I am unable to reproduce what Phergus is having issues with.

snikle · Post by **snikle** » Tue Jan 30, 2007 10:55 am

I can, sent trevor a screencap of it.

Post by **trevor** » Tue Jan 30, 2007 10:57 am

Got it. OK, I understand. scrollwheel+shift.

These are caused by the vision caching I put in. I knew there'd be places I'd miss that need a cache flush. Thanks for helping me find them.

I've got it tracked for b8.

Post by **dorpond** » Tue Jan 30, 2007 11:02 am

One thing I did notice that seem to be more of an aggravation more than anything.

When we change the facing of the token (with cone vision for example), it deselects the token so to reveal, we have to click on the token again and then reveal.

Seems like an extra step. Since we are already on that token, we should still be on that token ever after changing the facing - Know what I mean Trevor?

[edit]
I am talking when changing the facing in the token menu]