| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
there is "<" symbol in Landmarks name.
Modified the "<nolink>...</nolink>" clause parsing regexp to allow "<" in the middle.
|
|
displayed by another control.
- LLMenuGL in menu button replaced by LLToggleableMenu that handles visibility change upon clicks inside specific button rect.
- Added visibility change signal to LLToggleableMenu to update menu button pressed state.
- Added using menu handle in LLMenuButton.
|
|
|
|
|
|
|
|
|
|
clicking on user name in a nearby chat toast.
Now clicking an avatar name opens avatar profile; clicking an object name opens object inspector.
This change rolls back the fix of STORM-358.
|
|
closing on second click
- Changed type of gear menu buttons from LLButton to LLMenuButton in all sidebar panels where gear menu button is used.
- Added setMenuPosition(), setMenu() and updateMenuOrigin() to the LLMenuButton.
- Moved actions common for displaying a context menu to LLMenuButton::toggleMenu().
- In all sidebar panels where LLButton was replaced with LLMenuButton the following steps were taken:
1. setting gearMenu and its position relative to the menuButton with LLMenuButton::setMenu()
2. setting mouse down callback for the menuButton if needed.
3. calculating the menu origin point with LLMenuButton::updateMenuOrigin() in mouse down callback
|
|
|
|
The menu items can now be scrolled cyclically with a keyboard even if not all items are visible at once.
|
|
|
|
|
|
|
|
changed.
I'm not sure what the root cause of the problem was (maybe invalid initial selection in folder view),
but what seems to be definitely wrong is passing "scroll to rect" event
from *invisible* folder views up to accordion control, which is what I've fixed.
|
|
minimizing.
- Added signal to LLFloater that is emitted on minimize.
- Set minimize callback for appearance tab floater in LLSideTrayTab::undock. Method from LLSidePanelAppearance that handles camera issues
is called on minimization of floater.
|
|
|
|
|
|
Affected: My Outfits and Edit Outfit panels.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
change to better / more consistent naming
|
|
change to better / more consistent naming
|
|
let some LLViews handle shortcut keys if they want.
reviewed with ambroff
|
|
let some LLViews handle shortcut keys if they want.
reviewed with ambroff
|
|
(transplanted from 01d8534678f5613c924a036128addf6b7447c92a)
|
|
|
|
access functions, begin(), end(), etc.
this allows mutation of param block contents, without being able to change number of elements
|
|
|
|
|
|
|
|
logged in
reviewed by Monroe
|
|
|
|
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.
|
|
|
|
also popup notification is no longer a singleton
|
|
|
|
|
|
triggered by user taking an object from inworld into inventory
|
|
|
|
triggered by user taking an object from inworld into inventory
|
|
variables
|
|
|
|
Added ability to set max length in line editors by characters in addition to bytes
left other widgets (comboboxes/spinners) using the bytes, but it can easily be changed over
reviewed by Richard
|
