Ensure that full update interest list is re-established for the current region after a TP
Ensure that it works properly with both 360 and Area Search overlapping
Make the Developer menu full update toggle show current state and allow it to reset to 0/default when floaters are in use as an override.
Part 1: These changes prevent some of the aggressive culling that has prevented area search from working. They work best in combination with changes to the aggressive culling that better fit the viewer's memory footprint. These changes are committed separately to make it easier to change them
- getNameFromUUID can lead to wrong avatarNameCacheCallback callbacks.
For example the avatars name is not resolved/cached and gets first queried for owner (rlvacheck = true) then again for creator (rlva check = false). Result is a final callback with rlvacheck = false.
Thus handle all rlva name restrictions when the ui items get
created/updated/
- For attachments last owner usually equals the current wearer, this will leak the avtar name.
-> RLVa hide the last owner too.
* Radar, area search and sound explorer display "(Loading...)" when loading names since the UUID doesn't really help anything at all in the end anyway and might instead leak information when under RLVa @shownames restriction
* Area search shows complete avatar name instead of just username
* Sound explorer finally entered the age of display names and shows complete avatar name now
* Use sorting persistance already available in LLScrollListCtrl and remove specific asset blacklist debug settings
* Add right-click context menu
* Draw stripes for alternating lines for easier reading
* Add missing "Close" button
* Add filter editor for searching for particular assets
* Properly format date based on localizable format string and show time as local time instead of UTC
* Renamed classes to better fit the Firestorm naming system
* Removed unused methods
“This took a lot more work than the price column, as the data tended to be stale when first called. So, after taking advice from Techwolf Lupindo, I wound up having to hook into the message handler in llviewerobjectlist.cpp to add the data into the area search list as soon as it came available.
Since "…" is pretty common for "information is coming", and land impact can currently never be less than 1 much less less than 0.001, and it doesn't require translation, I took that route.
All in all the list looks clean, though the default column widths might benefit from some closer inspection: the price, LI and PC columns don't really need to be that wide.”
“Was pretty easy. I decided to follow existing code practice elsewhere and add the "free" statement to the column text for the L$0 purchasables. For the not-for-sale items, I couldn't quickly find or think of something that says so, so I just opted for a simple "--" - no need to make that able to be translated!
Tested to make sure the column shows correctly for objects, sorts correctly on the new column, and the column is able to be activated and de-activated.”
Beq