Age | Commit message (Collapse) | Author |
|
|
|
LLNotifications::ChannelMap went away when LLNotificationChannel became an
LLInstanceTracker subclass. Iterate the universe of channels using
LLNotificationChannel::beginInstances(), endInstances() instead.
More troubling is that LLNotificationChannel::getParentChannelName() went away
too. When LLNotificationChannel acquired a Params block and corresponding
constructor, it acquired the ability to listen on multiple upstream sources.
That meant that a single mParent string became inapplicable, and its access
method was removed. (Curiously, mParent was not itself removed, but it was
left unused.) Change mParent to mParents, a vector<string>, built by
connectToChannel(). Introduce getParents(), an accessor returning an
iterator_range over that vector.
Change LLNotificationsListener::listChannels() to collect a "parents" key in
the map returned for each channel, and -- for backwards compatibility --
capture the first entry in the "parents" array as "parent".
|
|
|
|
|
|
|
|
so singleton cleanup doesn't do things it really ought not do
|
|
|
|
there are no samples during the time period.
added hasValue to SampleAccumulator so we don't print a value when we don't have
a single sample yet
added some disabled log output for scene load timing
|
|
|
|
|
|
|
|
dependencies
|
|
|
|
|
|
|
|
foo to find some pointers
|
|
|
|
LLPostponedNotification now inherits from LLMortician so it can postpone its deletion. This prevents a crash when looking up an avatar name in the case where the name already exists in the cache.
|
|
|
|
notification form elements (buttonts) were added to the form. But then deserialized form elements were also being added to the form causing duplicate buttons. As a solution, only add on the deserialized form elements that exceed the amount in the template.
|
|
instead flash the conversation line item and Chat FUI button.
|
|
objectInfo was not being serialized/deserialized.
|
|
local disk per user.
|
|
reuse the functionality for do-not-disturb mode.
|
|
|
|
|
|
LLNotifications.
|
|
specified in notifications.xml. Also changes for CHUI 486, which allow the user to set preferences for hearing sounds for a New Conversation, Incoming Voice Call, Teleport Offer and Inventory Offer.
|
|
callback store the connection and disconnect on object destruction. This should help resolve some of the heap corruption we are seeing.
|
|
* Set max persistent notifications to 250
* Don't register for notification callbacks until after peristent ones are loaded.
reviewed with Simon
|
|
|
|
GCC does not allow local functor classes to be used with template algorithms, because template arguments must refer to an entity with external linkage.
|
|
and relog.
sort notifications in separate list
llnotification now uses param block to serialize to llsd
|
|
dismiss toast
removed special case logic for dealing with user online/offline collisions
added ability to cancel old duplicate notifications
|
|
- Added new tag called "footer" to the notification. This tag allows to display messages under the buttons in toasts.
- Created new class LLToastScriptQuestion for the "ScriptQuestionCaution" notification. This notification supports tag <footer>.
|
|
|
|
|
|
object inventory offers don't increment system menu count
added customizable merging behavior for duplicate "unique" notifications
fixed overeager notification channels
|
|
phase 2, removal of extraneous signaling in favor of llnotificationchannels
made notificationchannels work better with overrides and lifetime managed
by creator
|
|
phase 1, removal of most of llnotificationhandler
|
|
added Flag as value type
moved Batch to BatchBlock
renamed Choice to ChoiceBlock
made merging of parameters for ValueParams consistent (fillFrom and overwriteFrom are inverses of each other now)
made iteration over Multiple<T> type params easier
initial schema param blocks
|
|
into Minimal skin are declined and not present in inventory
made notification text skinnable
|
|
|
|
initial support for XUI auth dialog
|
|
|
|
|
|
|
|
|
|
|
|
Also started adding the tag 'fail' to entries in notifications.xml that are failures the user should always be told about.
Reviewed by Richard.
|