| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
connected to FB (otherwise, it autoconnects...)
|
|
matching the rest of the sRGB herd
|
|
|
|
account name
|
|
|
|
|
|
|
|
|
|
|
|
gamma exposed in settings
|
|
|
|
history code
|
|
issues, alpha-blend objects still missing haze underwater
|
|
|
|
|
|
|
|
|
|
skipping history, allow temporary url for display purposes
|
|
|
|
|
|
|
|
added options to web floater to hide history and disable buttons
|
|
show region names.
|
|
route should be called
|
|
FB token
|
|
|
|
|
|
|
|
|
|
|
|
Change LLControlVariable::mPersist from bool to tri-state enum. Its 'true'
value used to mean "persist only if changed from default;" third state now
means "persist regardless of value." Add forcePersist() method to set that.
Replace isSaveValueDefault() method -- used only by logic to determine whether
to save the variable -- with shouldSave() method to encapsulate ALL that logic
rather than only part of it. shouldSave() recognizes PERSIST_ALWAYS state.
When loading an unrecognized control variable from a user settings file, use
forcePersist() to ensure that we later save that variable again.
Tweak one of the unit tests to adjust for new semantics.
|
|
reflect/distort RTs
|
|
LLControlGroup::declareControl(), declareString() etc. etc. all used to return
BOOL -- which no one ever examines because it unconditionally returned TRUE.
Make it return the (possibly new) LLControlVariable* instead.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
A small, fixed set of cmd_line.xml switches can't reasonably be mapped to
settings variables, mostly because they affect the settings machinery itself.
Other than those, every new cmd_line.xml switch should map-to a settings
variable. Validate that only the known set does not have map-to; validate that
map-to variable actually exists.
|
|
|
|
fullbright+glow+texcolor
|
|
|
|
|
|
rendering
|
|
render
|
