Beta version 59 is now available to test! This time we worked on a mixture of fixes and improvements which cover a few different topics.
Hopefully the changelog should explain the update well enough.
Here is the full Changelog with all changes and fixes
- Fixed remote applications port not being saved
- Fixed ban client context menu not being shown when missing b_client_ban_create
- Fixed some icons being animated even when the client does not have the focus
- Fixed remote applications still being visible after removal
- Fixed disabling remote applications not doing anything
- Fixed event viewer pop-out not adjusting when resizing the server tree
- Fixed incoming pokes not being visible when hiding moderation events
- Hide channel create options when you cannot create a channel
- Improved behavior of links in pinned messages
- Improved remote applications event properties to be human readable
- Improved tooltips of sliders in audio settings
- Remote applications port is now set to default when input is cleared
- Updated chromium
Notes for this thread
Feedback as per always is welcome in this thread . Issues that are not related to this update belong to it’s own thread.
We suggest to place your wishes for upcoming releases in existing or new threads in the suggestion area instead of the release thread. We mention this because each update post will be closed after some days and the wish or suggestion could be lost.
We allow ourselves to delete all the off-topic posts from this thread.
I found a bug in that version: When you trying to change “Needed Talk Power” option while editing the channel, it isn’t showing the current value. Also i cannot set another value (error on 2nd screen). In beta-58 all worked fine.
I noticed that when I rename server/channel groups on the TeamSpeak server or change the icon of the group via the TeamSpeak 3 client, this is not applied in the TeamSpeak 5 client until I reconnect. However, changes to single permissions of the groups are already applied.
Client information Version: 5.0.0-beta59 Build Number: 1625645480 Build Date: 7/7/2021, 10:11:20 AM Chromium Version: 91.0.4472.114
Possible reason
Didn’t look pretty deep into it and only speak of own experiences. I expect it has something to do with the socket connection. If something get updated, the client loads all groups in it’s frontend / cache again but doesn’t clear the old entries from the array and so vue refreshes the html and displays the complete array and all duplicates.
Possible solution
If this is the real reason, the solution is pretty simple. Go into the function which handles this and add the missing array clear.
. Issues that are not related to this update belong to it’s own thread.
