summaryrefslogtreecommitdiff
path: root/indra/llmessage/llexperiencecache.h
AgeCommit message (Collapse)Author
2023-02-14DRTVWR-489-emoji: As part of the work to get macOS version of the Viewer ↵Callum Prentice
working, the flag was introduced to warn (and therefore error out) when a virtual override was not marked with the 'override' keyword. Fixing this up involved a large number of changes and this commit represents just those changes - nothing specially from the DRTVWR-489 viewer (Cherry pick of 3 commits from Callum to declutter the emoji PR: 3185bdea27b19e155c2ccc03c80624e113d312a6, 923733e591eb547ad5dfec395ce7d3e8f0468c16 and 6f31fabbc2d082b77c8f09bce30234ec9c506e33)
2020-09-02SL-13891 Coroutine creation was requested on exitAndrey Kleshchev
2017-03-30MAINT-7245 Use Experience Box in LSL Editor will not show as checked if ↵Mnikolenko Productengine
containing object is in another region
2016-09-15MAINT-5232: Normalize LLSingleton subclasses.Nat Goodspeed
A shocking number of LLSingleton subclasses had public constructors -- and in several instances, were being explicitly instantiated independently of the LLSingleton machinery. This breaks the new LLSingleton dependency-tracking machinery. It seems only fair that if you say you want an LLSingleton, there should only be ONE INSTANCE! Introduce LLSINGLETON() and LLSINGLETON_EMPTY_CTOR() macros. These handle the friend class LLSingleton<whatevah>; and explicitly declare a private nullary constructor. To try to enforce the LLSINGLETON() convention, introduce a new pure virtual LLSingleton method you_must_use_LLSINGLETON_macro() which is, as you might suspect, defined by the macro. If you declare an LLSingleton subclass without using LLSINGLETON() or LLSINGLETON_EMPTY_CTOR() in the class body, you can't instantiate the subclass for lack of a you_must_use_LLSINGLETON_macro() implementation -- which will hopefully remind the coder. Trawl through ALL LLSingleton subclass definitions, sprinkling in LLSINGLETON() or LLSINGLETON_EMPTY_CTOR() as appropriate. Remove all explicit constructor declarations, public or private, along with relevant 'friend class LLSingleton<myself>' declarations. Where destructors are declared, move them into private section as well. Where the constructor was inline but nontrivial, move out of class body. Fix several LLSingleton abuses revealed by making ctors/dtors private: LLGlobalEconomy was both an LLSingleton and the base class for LLRegionEconomy, a non-LLSingleton. (Therefore every LLRegionEconomy instance contained another instance of the LLGlobalEconomy "singleton.") Extract LLBaseEconomy; LLGlobalEconomy is now a trivial subclass of that. LLRegionEconomy, as you might suspect, now derives from LLBaseEconomy. LLToolGrab, an LLSingleton, was also explicitly instantiated by LLToolCompGun's constructor. Extract LLToolGrabBase, explicitly instantiated, with trivial subclass LLToolGrab, the LLSingleton instance. (WARNING: LLToolGrabBase methods have an unnerving tendency to go after LLToolGrab::getInstance(). I DO NOT KNOW what should be the relationship between the instance in LLToolCompGun and the LLToolGrab singleton instance.) LLGridManager declared a variant constructor accepting (const std::string&), with the comment: // initialize with an explicity grid file for testing. As there is no evidence of this being called from anywhere, delete it. LLChicletBar's constructor accepted an optional (const LLSD&). As the LLSD parameter wasn't used, and as there is no evidence of it being passed from anywhere, delete the parameter. LLViewerWindow::shutdownViews() was checking LLNavigationBar:: instanceExists(), then deleting its getInstance() pointer -- leaving a dangling LLSingleton instance pointer, a land mine if any subsequent code should attempt to reference it. Use deleteSingleton() instead. ~LLAppViewer() was calling LLViewerEventRecorder::instance() and then explicitly calling ~LLViewerEventRecorder() on that instance -- leaving the LLSingleton instance pointer pointing to an allocated-but-destroyed instance. Use deleteSingleton() instead.
2015-09-04Experience Profile to coroutines and Experience cache.Rider Linden
2015-09-03Region experience allow/disallow.Rider Linden
2015-09-03Moved group experiences into experience cache. Use coros and new HTTP libs.Rider Linden
2015-09-02Moved find experience into experience cache (moved cache recording into ↵Rider Linden
cache and out of UI) changed from responder to coroutine.
2015-09-02Move associated experience fetching into the ExperienceCache as a coro ↵Rider Linden
remove the responder.
2015-09-01MAINT-5575: Convert the Experience cache into a coro based singleton.Rider Linden
--HG-- branch : MAINT-5575
2015-08-31Some initial changes to convert the experience cache to a singletonRider Linden
--HG-- branch : MAINT-5575
2015-08-28MAINT-5575: Begin conversion to Singleton<> for Experience Cache. Commited ↵Rider Linden
on branch so that I don't trigger a build of it until I'm ready. --HG-- branch : MAINT-5575
2014-03-17Updated experience cache to get a const reference to xp datadolphin
2014-03-12Windows lets you erase with a const iterator but linux does not.dolphin
2013-08-21Added new fields to the experience cache.dolphin
Experience profile moved to it's own floater, will probalby be moving again. XP profile displays most data, though the presentation is not final Fixed a bug with the XP selection combobox in the script editor
2013-04-02Removed outdated experience property flagsdolphin
2013-03-13Fixed up expiration code for the experience cachedolphin
2013-02-13Updated experience cache to latest web service apidolphin
Added new CAP request for experiences the avatar can sign
2012-12-18Updated client to use new capsdolphin
brought over server changes to llExperienceCache
2012-11-26Added code for simulator integration.dolphin@dolphin-THINK.lindenlab.com
Added signals for cache update callbacks. Added expiration timers for cached experiences.
2012-11-19Test populating the experience keys UI with avatar name data.dolphin@dolphin-THINK.lindenlab.com
2012-11-14Mergedolphin@dolphin-THINK.lindenlab.com