| Age | Commit message (Collapse) | Author |
|---|
|
|
|
alpha/non/ALM/non-ALM
|
|
|
|
changes in CL 28424
|
|
|
|
|
|
glow
|
|
browser. Handle the dismiss case as best as possible.
|
|
|
|
focus properly...as to why an investigation is needed. For now explicly setting keyboard focus to the internal browser after it is displayed.
|
|
|
|
|
|
|
|
|
|
|
|
after launch
|
|
notification text for ACME-793
|
|
|
|
|
|
|
|
|
|
Previous CHOP-959 logic set a flag to remember that settings variable
RenderQualityPerformance was set (by --graphicslevel), so it could be applied
once LLViewerWindow is constructed. But on first viewer run, LLViewerWindow
constructor calls LLFeatureManager::applyRecommendedSettings(), which resets
that settings variable! So don't just set a flag, actually capture the
requested RenderQualityPerformance value for later.
|
|
SLShareHost setting from settings.xml
|
|
|
|
success notification
|
|
|
|
|
|
service host location as needed.
|
|
|
|
|
|
|
|
missing code block from previous change as per Dave P's advice
|
|
|
|
|
|
on state changes. Instead it returns true if the user successfully connected and false if the user successfully disconnected.
|
|
|
|
|
|
bullet-proof. Reviewed by Kelly
|
|
|
|
|
|
|
|
This really extended into the client-side request throttling.
Moved this from llmeshrepository (which doesn't really want
to do connection management) into llcorehttp. It's now a
class option with configurable rate. This still isn't the
right thing to do as it creates coupling between viewer
and services. When we get to pipelining, this notion becomes
invalid.
|
|
|
|
10.6.8 nV driver issues
|
|
goes blank if location is selected and a menu item is seleted
|
|
|
|
setting
|
|
|
|
|
|
|
