Astrolabe bug?

[myrroddin]

I'm reading change logs for various AddOns that use waypoints, routing, and Astrolabe. The consensus is there is a bug in Astrolabe, but I don't know what it is.

What I do know is that authors are using an API in TomTom to bypass the bug. If you could find out what that bug is, and why the API in TomTom works, you might find it of some use with your own waypoint code.

The API in question is found in TomTom.lua, starting at line 879:

function TomTom:AddMFWaypoint(m, f, x, y, opts)

[Zygor Dev 1]

We use a heavily customized version of Astrolabe, so that bug might not even be present in our code.

Do you have any more details on the kind of bug we're looking for? A crash, a bad map ID, a distance miscalculation?

[myrroddin]

I don't, but I might be able to ask around. If you use a customized version of Astrolabe, one would hope both your version and the version loaded by my other AddOns are both in memory. One isn't overwriting the other?

[myrroddin]

I got some feedback regarding Astrolabe's code, and where the bug might exist. Look at this forum thread for details: http://www.wowinterface.com/forums/s...ad.php?t=50496

In short, adding a waypoint by zone is broken, but if you specify mapID and floor number instead (different API) it will work.

[Zygor Dev 1]

We've been doing that for ages already Thanks for the effort though, it's appreciated.

As for overriding, no, ours uses a different version tag that doesn't clash with other copies.