| Age | Commit message (Collapse) | Author |
|---|
|
|
|
merging LLNearbyChatBar with LLNearbyChat;
clean up code; supressed a double creation of LLNearbyChat
|
|
|
|
dismiss toast
removed special case logic for dealing with user online/offline collisions
added ability to cancel old duplicate notifications
|
|
|
|
Notification handlers now use LLHandles to screen channels.
|
|
phase 1, removal of most of llnotificationhandler
|
|
|
|
then it obscures chatted text.
I repositioned the chat, move and camera floaters. Chat toasts now start 80 up from the bottom left rather than 10.
|
|
|
|
idle calls.
Reviewed by davep.
|
|
when chat window is minimized with chat history opened
|
|
Reviewed by Richard.
|
|
Richard.
|
|
- Nearby chat toasts flipped vertically
- Fixed notification and IM well floaters docking state saving.
|
|
also made toolbar buttons not trigger if enabled callback returns false
|
|
|
|
|
|
|
|
|
|
- LLBottomTray code and XUI removed.
- "Speak" buttom which resided in Bottom bar removed.
- Voice connection status update moved from LLBottomTray to LLVivoxVoiceClient.
|
|
EXP-1316 Minimized Snapshot floater has a snapshot preview image attached below.
EXP-1318 Clicking on nearby chat toasts should bring up Nearby Chat history
|
|
|
|
|
|
|
|
|
|
LLNearbyChatScreenChannel::showToastsBottom().
Apparently, a nearby chat toast got somehow destroyed while still remaining in the list of active toasts.
Attempt to sort active toasts in showToastsBottom() then triggered the crash.
I don't know how to reproduce the crash, i.e. force destroying a toast in a way that its onClose() method (which would remove references to the toast) isn't called.
So we'll just remove references to the toast whenever it's destroyed.
|
|
|
|
special case. Reviewed by Kelly
|
|
|
|
|
|
one in nearby chat toasts.
|
|
in-world are not added to Recent tab
- Add sender(only avatar) to the recent people list just after message appears in nearby chat
|
|
"LLChat" LLEventStream and pass incoming chat to it. Reviewed by Kelly.
|
|
|
|
|
|
|
|
(STORM-717) to develop a more generic one (applicable to all notification toasts).
|
|
|
|
* Normally toasts are as opaque as specified by "inactive floater opacity" setting.
* When mouse is hovering a toast, the toast uses "active floater opacity" setting.
* Fading toasts have 1/2 of "inactive floater opacity".
|
|
|
|
before it fades. Please add fade time back to Chat preferences.
- Added two spinners to the Chat preferences tab that control NearbyToastLifeTime and NearbyToastFadingTime
- Added callbacks to the LLNearbyChatScreenChannel that update these properties if they were changed
Refactoring of LLToast:
- Removed code that was making toast transparent from LLToast::draw()
- Modified LLToast interface that relates to showing and hiding toast, so that all screen channels can use LLToast universally.
- Replaced in LLScreenChannel calling methods of old interface to new ones.
|
|
|
|
|
|
|
|
|
|
|
|
all floaters).
The crash was introduced by my previous fix of this ticket in changeset 8ceebd3612f0.
The problem was that, suprisingly, even invisible (faded) toasts were destroyed when you hit Ctrl_Shift+W,
however they were still referenced by the toast pool, so the references were invalidated.
The easiest fix would be to remove all references to the toast being destroyed, no matter is it visible or not.
However, then we'd have to search for each destroyed toast in the pool, which is slow.
Besides, removing toasts from the pool compromises the whole idea of pooling (which was introduced to speed up creation of new toasts).
Another possible fix is not to destroy any nearby chat toasts when user hits Ctrl+Shift+W.
That would save us from any crashes at a price of changing existing behaviour (the toasts will remain visible).
So I went for a third option: when closing all floaters, skip invisible ones.
Then there won't be attempts to destroy invisible (pooled) toasts, so the crash won't happen,
and we don't seem to change any existing behavior.
However I'm not 100% sure of the latter statement, so the fix requires extensive testing.
|
|
|
|
Bug reason: The fix of EXT-1419 disables showing nearby chat showing toasts at all whenever you close one.
That was done to prevent a crash when viewer is exiting, but closing a toast manually should be handled differently.
Fix: If a toast is being closed (destroyed) manually, just remove it from the toast pool
(to prevent further references to the invalid pointer), but keep on showing new toasts.
I've overriden LLFloater::onClose() to differentiate the two cases.
|
