| Age | Commit message (Collapse) | Author |
|---|
|
inventory
applied Kitty's code changes listed in STROM-288 as it is a related issue and this
actualy fixed both issues!
|
|
|
|
|
|
|
|
|
|
|
|
after decreasing panel height
- Set height of scroll container the same as bounding panel's height
|
|
- Added localized tooltips for icons and info button in LLPanelTopInfoBar
|
|
- As the class LLToastNotifyPanel is deprecated, made the class LLToastScriptTextbox derived directly from LLToastPanel.
- Added callback for ignore button.
Now LLToastScriptTextbox has its own XML, therefore it's not needed to dynamically create toast panel.
Since LLToastNotifyPanel is deprecated all new notification toasts should be created this way.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
of the same object using external editor.
The bug was caused by using the object ID as temporary file name for editing script,
which of course didn't work for multiple scripts in the same object inventory.
The fix is to use MD5("object id" + "script inventory item id") for the file name.
|
|
loading big scripts or pasting a lot of text into script.
The bug was fixed by Satomi Ahn. Here is the description of what causes the problem from her comment in ticket:
"Disabling the loading of syntax keywords in LLScriptEdCore::postBuild() removes the freeze (and with it: syntax highlighting).
So it obviously comes from the parsing of the text.
I also noticed something else: by adding a llwarn in LLTextEditor::updateSegments(), I saw that this function was called a lot of times when loading a script, roughly once for each line in the script (naively I would have thought only necessary to update when finished... or to only update the new line).
My llwarn was in the "if (mReflowIndex < S32_MAX && mKeywords.isLoaded())", which means that, at each call, the text is actually parsed for all keywords... so the parsing of the script becomes quadratic instead of linear!!!"
- To fix this, Satomi added a flag depending on which parsing is disabled when it is not necessary.
|
|
honor floater opacity settings.
|
|
Make sure older toasts don't appear after newer ones fade out.
|
|
|
|
|
|
|
|
|
|
panels now follow opacity settings for inactive floater.
When the floater is active the thumbnails are opaque. The behavior is similar to texture control's.
|
|
|
|
Reason:
In viewer 2 ability was added to set aspect ratio while previewing textures. It was achieved by resizing the floater containing a texture, instead of proportionally resize the texture. The problem happened when multifloater was opened with texture preview floaters and for some floaters textures were not loaded yet. After texture was loaded, the floater (in multifloater) which contained just loaded texture resized to fit with the new texture's size and texture preview floaters screwed up from the multifloater.
Solution:
Proportionally resizing a texture inside the floater instead of the floater itself.
Also two issues was fixed: 1. when floater resized the texture streched in the floater and lost its proportions. 2. When docking texture floater to the multifloater, multifloater resized to fit with docked floater and other texture lost their proportions.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
viewer-development
|
|
|
|
|
|
|
|
|
|
transparency settings:
* 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".
|
|
|
|
(STORM-717) to develop a more generic one (applicable to all notification toasts).
|
|
mouselook mode.
- Fixed dereferencing a NULL pointer.
- Added EMAIL SNAPSHOT floater to the list of floaters allowed in mouselook mode.
|
|
panel, so you can go back if the landmark fails to load.
The bug was introduced in the fix of EXT-4700 (Creating a landmark brings up the Landmark sidepanel info twice).
To avoid reopening the "Create Landmark" panel, its Back and Close buttons were disabled.
However, the same fix removed the code for reopening the panel, so I can't see why we need to disable the buttons at all.
|
|
--fullscreen
disabled fullscreen mode for merge to viewer-development
|
|
when using orbit pan zoom tools.
better fix that uses tag to isolate all skin specific notifications
|
|
when using orbit pan zoom tools.
|
|
|
