Interesting. I didn't care for global coordinates as they are already covered
by lLGetInventoryData (Actually, I think it's already relative coordinates…
extrapolation from the tests I made. To be confirmed)
I could easily add a param type for "global/relative (?)" coordinates. As I
avoided unneeded searches, I think it's easier and faster to call the function
twice instead of getting a list and parsing it. It would be redundant with
llGetInventoryData, but maybe it's better to have it in the same function. And
maybe it will be faster (dunno yet)
For now, my function returns values depending on these constants:
osGetInventoryLandmarkParams (string landmarkname, int type)
LANDMARK_URL
secondlife://hostname:port:region/X/Y/Z/
LANDMARK_ADDRESS
hostname:port:region
LANDMARK_MAPSEARCH
http://hostname:port/ region
LANDMARK_GATEKEEPER
http://hostname:port
LANDMARK_REGION_NAME
region
LANDMARK_POSITION
<X,Y,Z>
--
http://www.speculoos.net/
secondlife://speculoos.net:8002/
Speculoos, the belgian cookie-flavored met averse
Le 13 mars 2012 à 23:07, BlueWall a écrit :
> Do you think that it would be worth the effort to return a list
> containing both the gatekeeper url and the global coordinates? The
> latter so that the distance can be calculated before trying to make the
> jump w/o needing to get that value from the dataserver.
_______________________________________________
Opensim-users mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/opensim-users
