MapTool 1.3 Bugfix Build 75

[LeopoldVonRanke]

I really am waiting for the semi-automated VBL drawing. Azhrei, will that make it into 76? That would be soooo coool....

Oh, and as far as I'm concerned, and for what it's worth: I would be completely fine to call this version feature complete after that. Just do some more debugging if there is anymore surfacing (such as in the VBL code or the image export), and call it final. Then progress - MapTool as it is right now is already fantastic. You've achieved quite something here with a free open-source tool.

[heyes]

I really am waiting for the semi-automated VBL drawing. Azhrei, will that make it into 76? That would be soooo coool....

Oh, and as far as I'm concerned, and for what it's worth: I would be completely fine to call this version feature complete after that. Just do some more debugging if there is anymore surfacing (such as in the VBL code or the image export), and call it final. Then progress - MapTool as it is right now is already fantastic. You've achieved quite something here with a free open-source tool.

Ditto.

[wolph42]

Just do Some more debugging...

roflmao

[Rumble]

I would be happy to have the next release be the final, 1.3-no-other-suffix Release version. Actually, I figured the .b## was going to be dropped around b65, so it's long overdue.

[Natha]

sooo... did anyone already run some tests with it? I'm very anxious to move my FW into B75 so I can merge it with my work on J's ontokenmove macro. But I don't want to step into a b71 trap. So basically: is it save?
(I did some testing with ontokenmove in 75 and it's all peeches)

I've used b75 to work on a few things but not in game situation yet. No problems to report.
I plan to use it in game twice next week, I'll let you know.

[Phergus]

sooo... did anyone already run some tests with it?

Worked fine for our 6-hour session last night.

[wolph42]

sooo... did anyone already run some tests with it?

Worked fine for our 6-hour session last night.

sooo... did anyone already run some tests with it? I'm very anxious to move my FW into B75 so I can merge it with my work on J's ontokenmove macro. But I don't want to step into a b71 trap. So basically: is it save?
(I did some testing with ontokenmove in 75 and it's all peeches)

I've used b75 to work on a few things but not in game situation yet. No problems to report.
I plan to use it in game twice next week, I'll let you know.

thanks and GREAT NEWS!! my congrats to te dev team

[LeopoldVonRanke]

Just do Some more debugging...

roflmao

I know, that sounds ludicrous -- but as someone who has done extensive debugging on a server/client system himself, with over 120 updates of a self-developed game with over 200 players at one point, I thought I had earned the privilege to say that in earnest: After feature freeze it is fine to keep gathering bug reports for a set amount of time, then go for a last haul for fixing those bugs, pray there will be no killer bugs in your last release -- and move on. I wish this tool all the best it can be. I love it.

[LaserWolf]

Template drawing issue still present in b75. It's bad enough to render the feature unusable for my players, unfortunately. I'm not sure how to recreate the issue, but if there's any way I can help isolate it I'm happy to pitch in.

[dorpond]

Template drawing issue still present in b75. It's bad enough to render the feature unusable for my players, unfortunately. I'm not sure how to recreate the issue, but if there's any way I can help isolate it I'm happy to pitch in.

Let me shift my focus and test this issue. If there is anything you can offer me to reproduce this, I will take it. Thanks!

[Edit: I tested and was unable to create any template drawing issue. Need more info.]

[jfrazierjr]

It may have to do with the whole high precision mouse thing that has caused some zooming issues. This is just a WAG, but could account for why it affects some people and not others.

[dorpond]

It may have to do with the whole high precision mouse thing that has caused some zooming issues. This is just a WAG, but could account for why it affects some people and not others.

Yeah, didn't that issue pertain to certain Microsoft Mice and that we really had no clontrol over it?

[Azhrei]

But I'm on a Mac using a Logitech mouse and I've seen it happen. It's a bug in MT, but I'm not sure where. I checked the mouse handlers and didn't see the x/y variables being screwed up anywhere.

[jfrazierjr]

But I'm on a Mac using a Logitech mouse and I've seen it happen. It's a bug in MT, but I'm not sure where. I checked the mouse handlers and didn't see the x/y variables being screwed up anywhere.

k, then thats not it. I have not had a chance to play in a few months, so in my limited testing have not seen it. Since Jay did some of the template code, perhaps he can take a quick look. It seems only be fairly recent builds that have this problem from what I have seen on the boards, so I wonder what changes may have inadvertently affected the templates(if any)

[dorpond]

But I'm on a Mac using a Logitech mouse and I've seen it happen. It's a bug in MT, but I'm not sure where. I checked the mouse handlers and didn't see the x/y variables being screwed up anywhere.

I am currently using a Logitech Wheel Mouse, Model: M-BD58
Works fine on my Windblows 7, 64 bit PC.

Do you know what version this broke?