Age | Commit message (Collapse) | Author |
|
messages popping is easier as per discussion with Oz and Boroondas also correcting some minor spelling issues
|
|
|
|
|
|
|
|
|
|
Trivial fix to add "/" to the search string.
|
|
People/Groups/Roles/Members.
Bug was caused by adding members with uncached names to search results- when name was uncached, method that added ids
to member list, didn't respect the filter.
- Fixed by adding members only when their names are cached and match the filter. If name is not cached, LLCacheName::get() is
called for such user id, and when name is cached, it calls function that handles adding of user to list depending on filter.
- Added default sorting of members by name, added saving of sort order to settings.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The point of this patch is to make the Mac updater code a bit more flexible
and reliable than it is right now. The issue is double:
* reliability: the string comparison code on the bundle identifier is not UTF8 compliant
* flexibility: the bundle identifier is hard coded to match the bundle identifier of LL viewer
(i.e. com.secondlife.indra.viewer) so it can't work for another viewer
(in particular, it didn't work for Snowglobe).
The "bundle identifier" is one of those Mac only thing stored in the Info.plist of a "bundle"
(the ".app" folder that's bundling an executable and all its resources and is seen
as an application when browsing with the Mac OS X Finder).
The patch fixes both issues:
* compare correctly UTF8 encoded strings
* allow the bundle ID to be passed as a parameter to the updater
The patch has really no consequence on LL viewer. It's more a matter of having cleaner, better code.
Author: Cypren Christenson
Ported and reviewed by: Merov Linden
|
|
|
|
This regression was caused by fix of STORM-126 in changeset 09f13edf6aa8 where adding of people from mInitialTargetIDs was removed.
And it was used to add people whom you P2P im'ed.
- Used mInitialTargetIDs to add people whom you P2P im'ed.
|
|
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.
|
|
|
|
web pages
|
|
against Boost-1.42)
|
|
command line options are given
used Aleric's SG2 changeset from http://svn.secondlife.com/trac/linden/changeset/3600
patching file doc/contributions.txt
Hunk #1 succeeded at 73 with fuzz 2.
patching file indra/newview/llcommandlineparser.cpp
Hunk #1 succeeded at 268 with fuzz 1 (offset -8 lines).
Edited doc/contributions.txt to create an entry for Aleric and moved the
issue ID there (patch wasn't able to place it at the right position,
lacking any context).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
has said something new" textbox that pops up in NEARBY CHAT window.
|
|
|
|
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
|
|
|
|
off of the Buy object floater
|
|
|
|
profile pic in friend request
|
|
|
|
|
|
|
|
Reason:
Each toast's panel lies on an invisible floater which is a bit bigger than the panel.
Notification toasts were displayed so close to each other that the floaters were overlapped by 2 pixels.
Because of the overlapping, toasts sometimes didn't receive mouse-leave events, thus not hiding their close buttons.
Fix:
Increased padding between toasts by 2 pixels (from 5 to 7) to eliminate overlapping.
|
|
away (all toasts used to freeze).
|
|
|
|
Groups.
Backing out changeset fe6c8e0a4a23 (which was made to fix STORM-263).
We'll examine and fix the faulty changes.
|
|
|
|
|
|
receive the Sorry you cannot change your display name until [time] message. They cannot access the change display name dialog to hit reset when throttled.
|