Age | Commit message (Collapse) | Author |
|
|
|
of AISv3 COPY library folder operation. (SH-4304)
|
|
in a non-bake region
|
|
|
|
instead of fetching a name
|
|
|
|
|
|
requests, removed many redundant calls
|
|
|
|
|
|
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.)
|
|
|
|
|
|
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.
|
|
The cmd_line.xml entries:
analyzeperformance
crashonstartup
debugsession
disablecrashlogger
logmetrics
logperformance
noquicktime
replaysession
all specify map-to settings.xml variables -- none of which existed! Introduce
such variables. Instead of detecting the presence of a particular switch in
the command-line parser, use the value of its corresponding settings variable.
|
|
build.sh LogScan greps for "error:" (among other things) so removing the colon
from the test name "syntax_error" should help.
|
|
|
|
Use map-to in cmd_line.xml to inform the command-line processor that the
target variable for --graphicslevel is RenderQualityPerformance.
That lets us eliminate clunky llappviewer.cpp switch from '0' to 0, etc.
Moreover, previous switch statement only accepted 0 - 3, whereas
LLFeatureManager::setGraphicsLevel() actually accepts 0 - 6. Introduce
LLFeatureManager::isValidGraphicsLevel() and use that to validate.
Replace switch statement in setGraphicsLevel() mapping int constants to string
literals with static vector of level names, using same data for mapping as for
validating level numbers.
|
|
removing minimum height enforcement, as changes are local-only and would not
be visible by other users in this repro, unless the user explicitly saved
the changes. Since there are many ways to get around the enforcement, and the
enforced minimums won't be visible to other users, its simpler to allow
users to use the full range of the hover slider.
NOTE: this means that a user's avatar can be underground, leading to the
camera pointing up at the sky. this is a known issue.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
UserLoginInfo block had <key>Value</key> without the required subsequent
element to provide any actual value. This confused at least the Python
LLSD reader.
|
|
|
|
|
|
updateClothingOrderingInfo. Also removed some wrong code for drag-and-drop corresponding to a case that's not allowed anyway.
|
|
|
|
|
|
and inadvertently being handled while marked text is selected.
|
|
It seems that certain build hosts have an (obsolete? broken?) install of
indra.util.llmanifest under the system Python. If we append the local repo
indra/lib/python to sys.path, viewer_manifest.py pulls in the broken
llmanifest. Prepend to sys.path instead to ensure we get the right one.
|
|
|
|
window as well
|
|
notifications simultaneously when he accept/decline friendship offer
|
|
inventory onto avatar’s name in resident picker)
|
|
exists(to enable "Chat history" menu item for Nearby chat)
|
|
|
|
viewer freeze
|
|
to conversation removes text entry prompt for chat bar
|
|
|
|
Also clarify comment for ELLPath in lldir.h: ELLPath int values are read from
settings_files.xml.
|
|
|
|
Requesting appearance updates on updateGeometry for the avatar was spamming
the back-end and causing the throttling mechanism to get hit. Removing that
caused a re-introduction of SH-4109, so added a callback to link creation
in the COF for attachments to request an appearance update.
This should cause us to request an appearance update once per attachment
attached, where before we were seeing up to 8 redundant requests.
|
|
updateCOF(), should need to go item-by-item fairly rarely.
|
|
updateClothingOrderingInfo()
|
|
Minor change in showHistory()
|
|
|