Age | Commit message (Collapse) | Author |
|
|
|
|
|
FB_POSTED state, for ACME-667
|
|
|
|
|
|
https://bitbucket.org/lindenlab/viewer-development-materials
|
|
xml of photo
|
|
|
|
|
|
request feed logic to use high/low-water level logic as is done
in viewer code.
|
|
|
|
|
|
https://bitbucket.org/lindenlab/viewer-development-materials
|
|
|
|
texture gamma corrections to spot inputs
|
|
|
|
we can included gamma ops
|
|
https://bitbucket.org/lindenlab/viewer-development-materials
|
|
|
|
can't see the status
|
|
|
|
|
|
|
|
ACME-652
|
|
|
|
|
|
|
|
OBJECT_ATTACHMENT_SURFACE_AREA
do not return to the 'no attachments' values after avatar removes last attachment
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
there are generally zero under water occluders.
|
|
|
|
|
|
demoting spotlights by removing their tex
|
|
Route --url and --slurl command-line switches through a common settings
variable. Treat them uniformly now. (Previously, passing --url would notice a
grid-specific SLURL and preselect that grid; --slurl wouldn't. Now both do.)
|
|
corrected related tooltips
|
|
|
|
Kelly.
|
|
|
|
|
|
editable
|
|
editable
|
|
I've never really understood the usefulness of displaying world-global
coordinates in the Help -> About box. It seems to me far more useful to know
where you are within the current region. If that proves problematic, we can
display both sets of coordinates -- but let's try it this way first.
|
|
The existing POSITION variable gives "global" position: that is, your region-
local coordinates plus the (somewhat arbitrary) global coordinates of the
region's corner within the whole world. That may be meaningful to people on
the mainland, hard to say, but it correlates with nothing else available from
the viewer. POSITION_LOCAL gives you region-local coordinates, which could be
used (for instance) to construct a SLURL.
|
|
|