I'm on a Mac using 1.26.12.20 and have encounter a game object that outputs players names and score in chat. Everyone else tells me they see peoples display name, all i see is this:
01:58 PM] Book of Dares whispers: secondlife:///app/agent/6a6d9c53-18b3-4929-a21e-c7a36311b916/displayname has 81 points.
Is this my issue or SL issue or Viewer setting or issue?
Neither... It's just one of those new SLURLs that got implemented in v3 viewers and got no equivalent (and no use) in v1 ones. But I really don't see why the scripter of the "Book of Dares" didn't use llGetDisplayName() to print their message instead of issuing such a SLURL... There's strictly no benefit at all to do what they did, and a huge drawback: incompatibility with some viewers (also, text clients).
[...] But I really don't see why the scripter of the "Book of Dares" didn't use llGetDisplayName() to print their message instead of issuing such a SLURL... There's strictly no benefit at all to do what they did, and a huge drawback: incompatibility with some viewers (also, text clients).
Probably because that's what the Second Life Wiki recommends ...
Quote:
If you merely wish to show the agent display name in the viewer window, it may be more straightforward to use Viewer URI Name Space, e.g.:
Probably because that's what the Second Life Wiki recommends ...
Indeed a stupid remark in the Wiki... I don't see how producing code that is only compatible with part of the clients (and with no text client at all) is "more convenient"...
For tomorrow's releases, I came up with a solution that doesn't involve adding a shitload of UI code bloat (and significant memory consumption overhead) like they did in the v3 viewer...
Here is how it will work: on receiving chat text or object IM text, the viewer checks for the presence of any app/agent/<uuid>/*name SLURL and, when it already got the name information for the corresponding avatar, it immediately replaces the SLURLs with the corresponding name (i.e. there is no need for complex callback method in that case, and all the member variables overhead it incurs in the v3 UI). When the name(s) is(are) not yet known (not yet in the name cache, which should be a rare occurrence since the objects are likely to emit messages about avatars around them), the viewer displays the SLURLs "as is" but clicking on them allows to open the Profile floater for the corresponding avatar (and next time the SLURLs will be emitted, the name cache will have the corresponding data and the name substitution will occur).
Users browsing this forum: No registered users and 67 guests
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot post attachments in this forum