| Age | Commit message (Collapse) | Author |
|---|
|
This reverts commit cbf64f875831992386dadc5a094b9739b678b764.
|
|
Straighten out muting to prevent echo when crossing from vivox to webrtc regions near a webrtc region boundary.
|
|
|
|
Release/2025.05
|
|
regions.
Muting was a bit random in the code, so it's now been straightened out and should
prevent echo.
Also, code was added to not attempt connection to non-webrtc regions in the webrtc code.
|
|
|
|
Basically a revert of SL-20206, 25388312cf28f8b30934ac3885783a96a3b2ed69
|
|
* Nearby tab slider
Add slider allowing users to adjust NearMeRange
* panel_people.xml adjustment
Add "m" after the NearMeRange slider distance.
* panel_people.xml avatar list fix
Adding NearMeRange slider caused avatar at the bottom of the nearby list to be cut off. Fix by reducing height.
* avatar list stepper adjustment
Noticed later that the bottom scrollbar stepper was still slightly cut-off. Reduce list height again by 3.
|
|
* Rich Presence w/o requiring access to friends list
Thank you Signal Linden for the pointer from https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Client.html#af0a85e30f2b3d8a0b502fd23744ee58e
"Note: On Desktop, rich presence can be set before calling Client::Connect, but it will be cleared if the Client connects. When Client is not connected, this sets the rich presence in the current user's Discord client when available."
This lead me to setting the Application ID here https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Client.html#ad452335c06b28be0406dab824acccc49 in place of setting it on
https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1AuthorizationArgs.html which would lead Authorize, GetToken, UpdateToken, Connect, and so on.
This means we don't even need the SecAPI saveCredential, loadCredential and deleteCredential parts now.
* Discord integration is enabled by default per spec
now that we don't need the user to authorise Discord SDK to have
any access to the user's friends list, etc. (which are Discord
Relationships related, and not needed just for Rich Presence).
* "Hidden Region" if Discord location sharing is off
instead of blank. The coords are hidden too, but the Party numbers
are still shown, for consistency with TPVs' implementations.
* Remove toggleDiscordIntegration declaration
The definition had already been removed, I had forgotten to remove
this one.
|
|
Url based handler for compact chat
Normal handling for expanded chat.
|
|
This reverts commit 68513b2d0b9f070aeabfc3cfff09d477006cd0a0.
|
|
This reverts commit 120e56754ccb3c6d7ab0da40e014701f2685b510.
|
|
|
|
|
|
|
|
|
|
it's own cache/cookie folder underneath the parent cef_cache folder. The whole cef_cache folder structure is purged at startup (before the parent being created at the first media instance creation)
|
|
The definition had already been removed, I had forgotten to remove
this one.
|
|
Noticed later that the bottom scrollbar stepper was still slightly cut-off. Reduce list height again by 3.
|
|
Adding NearMeRange slider caused avatar at the bottom of the nearby list to be cut off. Fix by reducing height.
|
|
Turns out it's not necessarily pulled by some other dependencies
on a fresh Arch installation.
|
|
|
|
instead of blank. The coords are hidden too, but the Party numbers
are still shown, for consistency with TPVs' implementations.
|
|
now that we don't need the user to authorise Discord SDK to have
any access to the user's friends list, etc. (which are Discord
Relationships related, and not needed just for Rich Presence).
|
|
Thank you Signal Linden for the pointer from https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Client.html#af0a85e30f2b3d8a0b502fd23744ee58e
"Note: On Desktop, rich presence can be set before calling Client::Connect, but it will be cleared if the Client connects. When Client is not connected, this sets the rich presence in the current user's Discord client when available."
This lead me to setting the Application ID here https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1Client.html#ad452335c06b28be0406dab824acccc49 in place of setting it on
https://discord.com/developers/docs/social-sdk/classdiscordpp_1_1AuthorizationArgs.html which would lead Authorize, GetToken, UpdateToken, Connect, and so on.
This means we don't even need the SecAPI saveCredential, loadCredential and deleteCredential parts now.
|
|
Add "m" after the NearMeRange slider distance.
|
|
|
|
handle/iter existed, but entry was null
|
|
Merge Develop into Maint-C (2025.06)
|
|
|
|
# Conflicts:
# indra/newview/llvoavatar.cpp
|
|
This reverts commit e05b32a0305f57573236c12dc4c1fbeecf2878ed.
Looks like I had a better fix in 2025.06
|
|
|
|
|
|
Add slider allowing users to adjust NearMeRange
|
|
Use NearMeRange to minimize difference with SLv
|
|
People were using fmod's undocumented capability to ignore everything
after the url to label their streams.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Full (user) name should suffice for the chat log, as it's the one
that is more of a reference anyway instead of display name.
The other avatar's display name is still displayed on the header
anyway. Seems like display names have higher chance of being empty,
that we would miss it being logged/notified because of that.
Also, now that we've optimised the avatars' positions' retrieval,
the numbers can come later after some avatar arrives, that getting
the position using the avatar's ID as the key would result in zero.
In that case, rather than reporting wrong distances (like 403996.2),
it's better to just skip distance information (it shouldn't matter
that much anyway).
|
|
|
|
|
