---
This is an automatically generated e-mail. To reply, visit:
http://codereview.secondlife.com/r/498/
---
(Updated Oct. 25, 2011, 6:03 p.m.)
Review request for Viewer.
Changes
---
---
This is an automatically generated e-mail. To reply, visit:
http://codereview.secondlife.com/r/507/
---
Review request for Viewer.
Summary
---
Fixed references to nonexistent
---
This is an automatically generated e-mail. To reply, visit:
http://codereview.secondlife.com/r/506/
---
Review request for Viewer.
Summary
---
Adding back code that was accid
---
This is an automatically generated e-mail. To reply, visit:
http://codereview.secondlife.com/r/505/
---
Review request for Viewer.
Summary
---
Ported the XML changes made for
Il giorno 25/ott/2011, alle ore 16:00, Lance Corrimal <
lance.corri...@eregion.de> ha scritto:
All I know about name caching is this:
clear your cache the hard way, by removing everything in the cache
folder, then open the info tab of a group with a really high number of
members, and your framera
All I know about name caching is this:
clear your cache the hard way, by removing everything in the cache
folder, then open the info tab of a group with a really high number of
members, and your framerate will go to hell until all display names
have been fetched.
Am Dienstag 25 Oktober 2011 s
For my solution to Storm-1653 (Group notices sent by muted residents
are still displayed) I have to call gCacheName->buildLegacyName to get
the AgentID associated with a legacy name.
It looks like this code may operate asynchronously if there is a cache
miss. In my testing I was always able to ge
