RPTools.net

i wonder if we are referring to the same thing here? i am talking about the fact that if you hover over an object with notes in it, the cursor changes to a hand and you can click it and view the notes. players should not be able to do this for objects that are not visible to them.

Ah, okay, there were two issues in the last build:

1. If you had NPC tokens that were not visible (blocked by topology or hidden in fog), by mousing over them you could see their name/label. This has been fixed.

2. If you hover over an object on the map, you would see the cursor turn to a hand and the notes are visible. I didn't check that when I tried it, but I can confirm that this has not been fixed.

please please please fix the z-order issues with stamps.

As soon as I host a server with a stamped map, half of my stamps forget thier z-order. It makes stamped maps unplayable. If I load my map up locally it shows up fine. As soon as I host a server the bug comes back.

The only way I have been able to fix it is by reloading the campaign each time a player connects.

I sent Trevor my XML file and he identified what is happening. He says he has a plan so I would expect this to get fixed soon.

Minor Bug: Deep zoom on visible image state

This is 99% fixed (I put it in the functional enough to use category) however there is still one outstanding issue to keep aware of.

If a token has an image state active on it, and you try to zoom "through" (zoom in really really really close) that token, you will get one of two effects. One, if a bit of the token that does not have the state image on the screen is zoomed in on, you will get a slowdown in processing. Two, if you try to zoom into the state image on the token, memory will start to become consumed (this is a slower rate that the B47 issue).

You can zoom in to your heart's content anywhere else on the map as long as a token with visible image state is not in the active view.

If I set an object to Free Size and zoom out, the free size gadget in the bottom right corner doesn't scale, so it soon becomes larger than the image itself. But because the gadget eats up any mouse events that it doesn't understand, I can't right-click on the object to access the ontext menu. Instead, I have to zoom up until some portion of the image is available, do the right-click function, then zoom back out.

Help?!

Right-click in the Map Explorer works.

Question:

I'm seeing some dialog-drawing issues now and again with my macros (as well as with the token properties dialog). Basically, it will sometimes pop up as a blank frame, and will not draw in the buttons or fields. Usually, canceling out and reopening a couple times brings the dialog up as expected.

I don't recall having this issue before, but I also have vastly more complex macros, so it might just be a memory issue or screen redraw problem on my end (at least for macro-generated dialogs and input()'s). However, if it's not - or if others are seeing the same thing - I wanted to raise it to the devs' attention.

Yea several people have has this issue with any of the pop up windows in the past. If you switch to another window then back to MT it should display the window without the need to keep reopening it. As for what causes it I don't know.

Ah. I find it usually draws if you expand the border of the dialog slightly.

However, I think I now have some other bug. In the campaign linked below, I have observed unusual behavior. For background:

Each token has a set of string properties that contains the relevant information about their powers. This information is read by a number of different macros (used for attacking, etc.).

Now, when I open the campaign and edit a token, I sometimes see the collection of token properties, including the property strings called Power0, Power1, and so forth. They are properly filled out (in the format "powername=Great Cleave; action=standard; usage=encounter;" etc. etc.)

At least, in some cases.

For some tokens - especially after I run the short rest macro - the token's properties appear to be wiped out. However, if I run a macro (such as "Power Use Tracker") that reads and manipulates those properties, it still works.

I can't figure it out, but there's some sort of display issue here. As far as I can tell, the properties still exist, but they are not visible in the token editing screen - and they don't ever come back, even when MapTool is closed and reopened. They exist somewhere, but are not editable in the token properties screen.

Any thoughts?

http://www.houseofgenius.com/files/dd4e-template3.cmpgn


Edit: forgot to add, I'm running MapTool b48 (obviously), starting from the 1G batch file, and I have the stack size set to 1M.

Edit again: removing the "setProperty" lines from the short rest macro in the campaign sometimes prevents the disappearing properties thing, but not always.

Running setProperty() for a token property that exists for that token type will cause problems for the token property editor dialog if you set the value to a number. The value is still there, just the token property editor will not display it.

A fix has already been created.

Well that'll explain it right thar. Thank you - I had missed any previously posted information on that. That is a bit of a relief, actually.

I hit this problem quite frequently on Ubuntu 8.04 (Sun JDK 1.0.6_06) with that past several version of MapTool. It will happen randomly with any dialog in the program. Closing and reopening the dialog usually fixed this. The only error I get is on program startup.

I will try to recreate the problem with an strace.

Edit: Okay, found the fix. It's a problem with Compiz/Beryl and Java Swing. To fix you just have to add the following to your .bashrc/.profile

Reference here

Update on the "Big Macro go BOOM!" problems.

I have identified many areas where complex macros are causing the regex expressions to error which causes the problem where the macro does not run at all and you are just left with the macro text in the input box.

I have fixes for some which will appear in a patch some time. Some of the others are proving to be more difficult and will take longer to fix.

In the mean time if you want to try avoid the problems these are the steps you should take (in the order of what is most likely to blow up).

• Keep {} to a minimum in a macro.
  The more sets of {} in the macro the more likely it is to blow up. This is not referring to fact that you can only have two levels {} deep, but sequential {} blocks, the more you have the more likely it is to blow up. This limit is per macro so calling multiple macros with a small amount of {} blocks will not case the problem.
  
• Prefer " quotes over '. Both can blow up but ' will do so faster (you really need a LOT of strings to have a problem with ").

There are likely to be more conditions that cause the issue that I havent found yet but these are the most common, it is probably a good practice to split your macros up and call them with [macro(): ] where you can

One more step you can take to avoid macros going boom was announced/discussed in this thread in the MapTools forum.

If you are having trouble with your macros going boom and can't solve it by streamlining code like Craig described, try downloading MapTools instead of using the webstart, and edit the batch file to something like this:

java -Xmx512M -Xss1M -jar maptool-*.jar run

The -Xss1M is the part that affects macro boomage, and setting it to this value should be good enough to run all the common macros we've seen so far on the forums.