The llMapDestination example provided in this article doesn't work, should it be removed? Day Oh 13:05, 9 September 2008 (PDT)
Also, I couldn't reproduce the shout on DEBUG_CHANNEL, but I'm not sure whether it's a bug. Day Oh 13:06, 9 September 2008 (PDT)
That example needed a state_entry event. The debug channel thing should probably be reported as a bug if it's reporting an error that isn't on DEBUG_CHANNEL (if it's not reporting a bug... that's a different issue). Never crossed my mind to check this but it might also accept UUIDs. -- Strife (talk|contribs) 17:27, 9 September 2008 (PDT)
How do you get the landmark's region?
Landmarks are region specific. While this function gets the position, within its region, that a landmark points to, it tells me nothing of what region that landmark pertains to. So, one can't discriminate between landmarks in a prim's contents for specific regions. With this function, one can, and can only, apply the location data of any landmark for any region within the local region only.
It is possible, I suppose, in a cumbersome way, to get the region from the landmark name, if the name hasn't been changed. But then, you can also get the position from the name, in the same cumbersome way, if the name hasn't been changed or truncated. So, this seems to be a sort of odd, over-burdened (needing a dataserver call) function to get just a single bit of information for one specific inventory type, that, then, isn't even exclusive. LeRoi Sautereau (talk) 07:07, 4 December 2015 (PST)
- Yep, llRequestInvetoryData is pretty useless. -- Strife (talk|contribs) 13:52, 5 December 2015 (PST)
- Edit: You could do a request to GridSurvey with the grid position (global_position/256) to get the name. E.G. http://api.gridsurvey.com/simquery.php?xy=999,1001&item=name -- Strife (talk|contribs) 13:59, 5 December 2015 (PST)