MapTool 1.3 Development Build 57

[Thargor]

I got pretty much what you'd expect - it asks for the value of "test" over and over. Are you getting something different?

If your maptools froze, than I got the same

[Hawke]

I had mentioned this before, it's looking for a variable that isn't there and the trigger is run several times. I don't think it'll make it in 1.3, but I suggested there be some kind of error checking for the statsheet... something like excel #ERROR if the statsheet references a property that doesn't exist. A typo can hurt you.

The number of dialogs is not infinite though. Move your mouse off the token and eventually you'll click through the dialogs. I think you can edit the token properties through the map explorer to make the fix.

[trevor]

it asks for the value of "test" over and over.

as in never stops asking ?

[Azhrei]

Correct, Trevor. The word "test" in brackets is a request to the macro language for that variable and the macro language puts up a prompt if such a variable doesn't exist. This is great functionality in the context of a macro, but doing this in a property that will display on the statsheet is problematic.

A possible solution is to flag the macro library so that it knows a statsheet value is being interpreted and do what Hawke suggests and display "#UNDEF(test)" or something similar. (Having the variable name in the error message would be a huge step towards finding and correcting the problem!)

But that would be a bit of a hack since it would be some kind of global state flag that the statsheet processor would set, evaluate the properties, then reset when it's done. Perhaps adding a flag to the method that evaluates properties that says, "user interaction allowed" would suffice? Then it's not a global flag. And it's easy to implement with an overloaded method that takes an additional parameter (the original method is modified to call the new one with TRUE being passed).

But I'm not familiar with how property values are retrieved...

[RPTroll]

I'm late to the party on this but... You can do computed properties in the stat sheet?

[trevor]

I'm late to the party on this but... You can do computed properties in the stat sheet?

Uhm .... yes

[trevor]

The word "test" in brackets is a request to the macro language for that variable and the macro language puts up a prompt if such a variable doesn't exist.

heh, that is one of the few features that I actually wrote for the macro stuff

What I wasn't aware of was the side affect of the property sheet. Yeah that's kinda sucky.

For now the best work around is: don't do that

[Hawke]

For now the best work around is: don't do that

Hehe. It only happens when you typo a variable for me... I type in [TotaAC] instead of [TotalAC]

I'm late to the party on this but... You can do computed properties in the stat sheet?

Example... set your AC to [BaseAC+ACBonus] and your statsheet will show your current AC... if you get a temp bonus because of a power just set ACBonus to 1 and you'll then see it correctly in the statsheet.

Just don't type [ABConus] or MapTool will be angry at you. =)

[trevor]

Just don't type [ABConus] or MapTool will be angry at you. =)

Oh, right, good point

[RPTroll]

Hmmmm. Possible serious, maptool ending hosage. That leaves me no choice but to try it out.

[patoace]

I'm late to the party on this but... You can do computed properties in the stat sheet?

Computed properties? You can run macros on mouseover!

See here

http://forums.rptools.net/viewtopic.php ... 14#p118814

[RPTroll]

I really should read the forums more often. <sigh>

That is pretty freakin' cool.

[Hawke]

I really should read the forums more often. <sigh>

That is pretty freakin' cool.

Hehe. If you do get that error, Az informs me that the popup boxes shouldn't be infinite... eventually you can close them all. Just quickly move your mouse away and try esc or enter or something to get through them.

[Rumble]

I really should read the forums more often. <sigh>

That is pretty freakin' cool.

Hehe. If you do get that error, Az informs me that the popup boxes shouldn't be infinite... eventually you can close them all. Just quickly move your mouse away and try esc or enter or something to get through them.

I've found that occasionally just Alt-Tabbing away from the window and then back halts an endless progression, but then, that's with null pointer errors. Dunno about mouseover stuff (though I expect that the bigger and nicer your resolution, the longer those popup windows will take).

[lmarkus001]

Tried b57 tonight, but had critical failures that prevented using it, so had to revert to b56. Will send the campaign file and more specifics when I am more conscious!