On 2008-10-29, at 18:01, SignpostMarv Martin wrote:
The current system relies on integers for grid co-ordinates and though
the function llGetRegionCorner() returns a vector, the values are
practically integers also.
I'm not sure I understand this. Region coordinates are floating point
numbers, and whether they are or not... 512 and 1024 are perfectly
good integer and floating point values. What does the fact that
they're integer or floating point have to do with anything? Grid
coordinates can be multiples of 256, 512, 1024, etcetera.
As for object movement code that relies on a 256x256 dimension, I'm
not
sure how many there are (with the exception of inter-sim warpPos
teleporters) that make such calculations, since CHANGED_REGION would
still fire correctly.
There's teleporters that check to make sure you're specifying a
region in sim, scanners that check for impossible coordinates
sometimes returned by sensors, physical and non-physical objects that
need to check to see if they're likely to go off-world, etcetera,
etcetera, etcetera.
We need to add a region size call NOW, if this is ever going to be
changed.
_______________________________________________
Policies and (un)subscribe information available here:
http://wiki.secondlife.com/wiki/SLDev
Please read the policies before posting to keep unmoderated posting privileges
