summaryrefslogtreecommitdiff
path: root/indra/newview/llavataractions.cpp
AgeCommit message (Collapse)Author
2019-04-10SL-10927 FIXED [EEP] Unable to share environment settings from My ↵maxim_productengine
Environments floater
2017-12-14MAINT-8089 FIXED User A can't unblock text from user B when use right-click ↵Mnikolenko Productengine
menu in chat
2017-05-17MAINT-6805 Fixed Right-click menus in the right and left panes of the ↵andreykproductengine
Conversations windows are different
2017-05-15MAINT-7383 show notifications for Purge item action in all inventory panelsMnikolenko Productengine
2017-05-04MAINT-7383 Revise notification for Empty Trash / Purge trash action to ↵Mnikolenko Productengine
include number of items being deleted.
2017-02-15MAINT-7118 Swapping legacy people API with new cacheandreykproductengine
2016-11-14Merged in lindenlab/viewer-cleanupAndreyL ProductEngine
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.
2016-08-29MAINT-1768 Previous changes are reverted. Sharing items from trash is ↵Mnikolenko Productengine
disabled now.
2016-05-19Merged in lindenlab/viewer-releaseAndreyL ProductEngine
2016-05-06merge 4.0.4-release and MAINT-5974Oz Linden
2016-04-11MAINT-6273 "Freeze" and "Eject" menu items are added to Nearby context menu.Mnikolenko Productengine
2016-03-02MAINT-5362 Adding/detaching/taking off etc from the inventory view in ↵Mnikolenko ProductEngine
appearance panel will add/remove the wrong item if a different item is selected in inventory floater
2015-11-10remove execute permission from many files that should not have itOz Linden
2015-03-16MAINT-4974 FIXED Complete name should be used in ↵Mnikolenko ProductEngine
LLAvatarActions::buildResidentsString only when building name string for share confirmation dialogs
2015-01-16MAINT-4799 FIXED Show complete avatar names in confirmation dialog.Mnikolenko ProductEngine
2014-05-23MAINT-4081 FIXED When removing a friend, the dialog now mentions complete nameAndreyL ProductEngine
2014-05-07Merge downstream version 3.7.8 codesimon
2014-05-06MAINT-423 FIXED Unminimize session floater and select this session when ↵maxim_productengine
sharing initiated.
2014-04-22MergeXiaohong Bao
2014-04-21Merge downstream codesimon
2014-03-26MAINT-2376 FIXED Centre the map on friend's locationMnikolenko ProductEngine
2013-11-25MAINT-3320 : Make inbox (Received Items) more resilients to deletion while ↵Merov Linden
we're at it
2013-11-06merge with releaseRichard Linden
2013-08-29MAINT-3075: don't display the target user name as a SLURL in the ↵Oz Linden
RequestTeleport dialog
2013-08-09second phase summer cleaningRichard Linden
replace llinfos, lldebugs, etc with new LL_INFOS(), LL_DEBUGS(), etc.
2013-07-30Summer cleaning - removed a lot of llcommon dependencies to speed up build timesRichard Linden
consolidated most indra-specific constants in llcommon under indra_constants.h fixed issues with operations on mixed unit types (implicit and explicit) made LL_INFOS() style macros variadic in order to subsume other logging methods such as ll_infos added optional tag output to error recorders
2013-07-29STORM-1838 Add display name handling to the initial notificationJonathan Yap
2013-06-06STORM-1838 Added teleport request to conversation log. Added xml to have ↵Jonathan Yap
message appear in IM window, if open. Code cleanup.
2013-06-05STORM-1838 Slowly reappling changes to work with CHUIJonathan Yap
2013-03-18merge up to 3.5.0-beta3 (chui)Oz Linden
2013-03-12CHUI-809 FIXED Changes in menu items to make them consistent. Do not start ↵Mnikolenko ProductEngine
IM if selected person is self.
2013-02-22CHUI-633 FIXED User is not able to open chat history by 'View chat history' ↵maksymsproductengine
menu item from pop-up menu of People floater
2013-01-30CHUI-647 FIX "Conversations" floater is not opened when user wants to share ↵Cho
something via "Conversation log" floater Added call to show conversations floater in LLAvatarActions::share
2013-01-25STORM-1838 Minor UI improvements and code changesJonathan Yap
2013-01-24STORM-1838 Break out a large block of code from handle_lure_callback so it ↵Jonathan Yap
can be called directly by teleport_request_callback.
2013-01-24STORM-1838 Add optional message processingJonathan Yap
2013-01-18merge up to 3.4.4-releaseOz Linden
2013-01-18STORM-1838 Removed block of commented out codeJonathan Yap
2013-01-11STORM-1838Jonathan Yap
2012-12-17Merge with viewer-chuiMerov Linden
2012-12-17CHUI-580 : WIP : Protect callback connections passed to ↵Merov Linden
LLAvatarNameCache::get() where necessary
2012-12-13CHUI-599 : Fixed : Avatar name provides now a method to get the regular ↵Merov Linden
account name.
2012-12-05CHUI-580 : WIP : Change the display name cache system, deprecating the old ↵Merov Linden
protocol and using the cap (People API) whenever available. Still has occurence of Resident as last name to clean up.
2012-11-27CHUI-544 (Legacy name shows in conversation list for user that answers a ↵MaximB ProductEngine
voice call)
2012-11-20CHUI-447 Additional fix(Show only display name for user that starts ↵maxim_productengine
conversation )
2012-11-09CHUI-337 FIXED: To avoid confusion with a classes "...conversation..." and ↵AlexanderP ProductEngine
in accordance with the naming convention in the project, some classes and corresponding files should be renamed: LLIMConversation -> LLFloaterIMSessionTab LLIMFloater -> LLFloaterIMSession LLNearbyChat -> LLFloaterIMNearbyChat LLIMFloaterContainer -> LLFloaterIMContainer LLNearbyChatBarListener -> LLFloaterIMNearbyChatListener LLNearbyChatHandler -> LLFloaterIMNearbyChatHandler
2012-11-08CHUI-484: Updating the code to rather than refer to it as Busy Mode, it now ↵William Todd Stinson
refers to it as Do Not Disturb mode.
2012-10-26CHUI-383: Realized that prior changes for this bug caused a regress. The ↵Gilbert Gonzales
regress was using the people panel or a notecard to start a im/call with a user. When doing this the conversation line item would not be focused. Resolution: Changed all calls to LLIMFloater::show() to LLIMFloaterContainer::showConversation(), which will first select the conversation line item and then show the corresponding conversation floater.
2012-10-17CHUI-422 : Update the ad-hoc conversation with the known list of on line ↵Merov Linden
agents without waiting for server message (which often doesn't come...).