llRequestInventoryData and/or llMapDestination and Mac Leopard

I am not in the position to test this out since I don't own a Mac. I'm wondering if those that do could check this out for me or tell me if you've had similar problems.

I use llRequestInventoryData(LandmarkName) to get the global coordinates of a landmark in the object's inventory of a HUD worn by the AV. The data is of course returned in the dataserver event as:

dataserver( key vKeyNull, string vStrData )
    {
        if (vKeyNull == g_LM)
        {
            // gets the landmark coordinates and feeds them to the map
            g_LM = null_key;
            llMapDestination( llGetRegionName(), (vector) vStrData, ZERO_VECTOR );
        }
    }

This is all pretty standard stuff. It works 100% reliably on any Windows computer. A Mac user of my HUD teleporter that incorporates this code IM'ed me saying it did not work correctly on his Mac. He is saying that it will give the correct results when trying to TP from his home sim, but fails if trying to TP from anywhere else. He gets sent somewhere else or the location is reported as invalid.

I suspect that this is a bug with the Mac, since it works fine on any Windows computer. He even tried the same object on his PC and it worked fine. I suspect that either the coordinates being returned are incorrect, or it's returning the Region name incorrectly.

I'm wondering if anyone with a Mac has encountered a similar problem or would be willing to test this out. I haven't found any mention of it in the JIRA.

I can confirm that...

Mac OS-X Leopard, with regular viewer or RC 1.20 (latest version)...

It's even worse than you describe. As far as I understand, the llMapDestination should open up the Map and show the location in the LM on it... This doesn't happen. The destination vector is fetched ok (checked it through llOwnerSay), however, the map doesn't open up and if I have it open and touch the object, the coordinates are not transferred to the map.

Guess that's worth a JIRA...

It's been buggy for some people for a long time.

http://jira.secondlife.com/browse/VWR-2060
http://jira.secondlife.com/browse/VWR-1405

Yep is the same problem as reported in VWR-1405. It is a different problem from VWR-2060. I tried the solution reported there and it did not work. mmm, VWR-1405 never came up in my search using llMapDestination as keyword.

Thanks for the input folks. Like usual, we will have to wait for the Lindens to get around to it. I don't think we should hold our breadth though. This was originally reported close to a year ago and is still unassigned.

I've linked the two issues.