For registered users, the server will now remember their channel
listeners (and their volume adjustments) and will restore them once the
user rejoins this server.
This prevents adding all targets in said subdirectories to the ALL
target by default. Instead, only those targets that are explicitly
referenced (e.g. via target_link_libraries) are built.
This also has the side-effect that any install-directives in these
subdirectories are also ignored for the default install targets which
prevents these libraries of unconditionally installing themselves when
issuing a make install. Instead, we now have to make any 3rdparty
component that we do indeed want to install, do so explicitly (e.g. via
install_library()).
Previously we would define our install paths as relative paths when
using the packaging option and turning them into absolute paths
otherwise.
While relative paths are required for CPack to work properly, we use
the paths e.g. for passing them in via macros and there we absolutely
require the full, absolute paths to be passed.
Thus, this commit removed the discrepancy of the results when built with
packagin=ON vs packagin=OFF and now always defines the install paths as
relative paths. However, we now keep an additional set of paths around
that are now always absolute.
The auxiliary files will now make use of configure_file in order to
ensure that e.g. the binary names used in them always match the names of
the actually built binaries.
Previously the server was only looking for files named e.g. murmur.ini
or murmur.sqlite. With this commit, the server will now look first for
files called mumble_server.ini and mumble_server.sqlite before falling
back to the old names (for backwards compatibility).
This is meant as a means to drive forward the server renaming from
murmur(d) to mumble-server.
Applying clang-format to this source file actually invalidates the
file's syntax rendering it un-parseable by the
generate-ApplicationPalette-class.py script.
Opus has been the go-to codec for years now and there is absolutely no
reason why one would want to use any of the legacy codecs (Speex or
CELT) its stead.
Thus, this commit completely removes the support for these codecs from
the Mumble client.
Incidentally, having different codecs available somehow even caused some
audio artifacts, which should now be resolved as well.
Fixes#4538
Currently translated at 100.0% (2099 of 2099 strings)
TRANSLATION: Update Turkish translation
Currently translated at 100.0% (2095 of 2095 strings)
TRANSLATION: Update Turkish translation
Currently translated at 100.0% (2093 of 2093 strings)
Co-authored-by: Hosted Weblate <hosted@weblate.org>
Co-authored-by: Oğuz Ersen <oguz@ersen.moe>
Translate-URL: https://hosted.weblate.org/projects/mumble/mumble-client/tr/
Translation: Mumble/Mumble Client
Currently translated at 100.0% (2095 of 2095 strings)
TRANSLATION: Update German translation
Currently translated at 99.9% (2094 of 2095 strings)
TRANSLATION: Update German translation
Currently translated at 99.9% (2092 of 2093 strings)
TRANSLATION: Update German translation
Currently translated at 99.9% (2092 of 2093 strings)
TRANSLATION: Update German translation
Currently translated at 100.0% (2093 of 2093 strings)
Co-authored-by: Hosted Weblate <hosted@weblate.org>
Co-authored-by: Robert Adam <dev@robert-adam.de>
Co-authored-by: Vri 🌈 <weblate@vrifox.cc>
Translate-URL: https://hosted.weblate.org/projects/mumble/mumble-client/de/
Translation: Mumble/Mumble Client
Currently translated at 100.0% (2093 of 2093 strings)
TRANSLATION: Update French translation
Currently translated at 100.0% (2101 of 2101 strings)
Co-authored-by: Hosted Weblate <hosted@weblate.org>
Co-authored-by: John Doe <thraex@numericable.fr>
Translate-URL: https://hosted.weblate.org/projects/mumble/mumble-client/fr/
Translation: Mumble/Mumble Client
Currently translated at 90.4% (1898 of 2099 strings)
TRANSLATION: Update Norwegian Bokmål translation
Currently translated at 90.2% (1892 of 2096 strings)
Co-authored-by: Allan Nordhøy <epost@anotheragency.no>
Co-authored-by: Hosted Weblate <hosted@weblate.org>
Translate-URL: https://hosted.weblate.org/projects/mumble/mumble-client/nb_NO/
Translation: Mumble/Mumble Client
Currently translated at 100.0% (2099 of 2099 strings)
TRANSLATION: Update Polish translation
Currently translated at 100.0% (2096 of 2096 strings)
TRANSLATION: Update Polish translation
Currently translated at 100.0% (2095 of 2095 strings)
TRANSLATION: Update Polish translation
Currently translated at 100.0% (2093 of 2093 strings)
Co-authored-by: Hosted Weblate <hosted@weblate.org>
Co-authored-by: Matthaiks <kitynska@gmail.com>
Translate-URL: https://hosted.weblate.org/projects/mumble/mumble-client/pl/
Translation: Mumble/Mumble Client
Currently translated at 99.9% (2097 of 2099 strings)
TRANSLATION: Update Chinese (Simplified) translation
Currently translated at 100.0% (2096 of 2096 strings)
TRANSLATION: Update Chinese (Simplified) translation
Currently translated at 100.0% (2095 of 2095 strings)
TRANSLATION: Update Chinese (Simplified) translation
Currently translated at 100.0% (2093 of 2093 strings)
Co-authored-by: Hosted Weblate <hosted@weblate.org>
Co-authored-by: deluxghost <deluxghost@gmail.com>
Translate-URL: https://hosted.weblate.org/projects/mumble/mumble-client/zh_Hans/
Translation: Mumble/Mumble Client
This introduces a new global shortcut that can be used to start or stop
listening to a configured channel.
Fixes#4486
Co-Authored-By: timjwkim <timjwkim@umich.edu>
Up to now the logic for clearing shortcut data upon a change in the
shortcut config window was to see if the type() of the current data
matches that of the shortcut's default data. However, for user-defined
types QVariant::type() always returns QVariant::UserType and thus
different user-defined types could not be distinguished.
If we instead use QVariant::userType(), this problem does no longer
exist.
When storing shortcuts in the database (which happens only for
server-specific shortcuts), the assumption has been that the type of the
stored shortcut is always "Whisper/Shout" because up to now this is the
only shortcut that can be server-specific.
However, this approach is not very future-proof, which is why this
commit makes sure that from now on, we explicitly store the type of the
shortcut as well.
Previously, the Mumble version was encoded with a uint32
in the network protocol reserving 2 bytes for the major
component and 1 byte for each minor and patch.
The versioning format was changed to include a build
number in the patch field. With a recent update (1.4.274)
the patch field exceeded 255 for the first time and broke
the protocol version.
This commit completely reworks how the version is stored
internally and transfered with the network protocol.
The new version is a uint64 and consists of 4 fields with
2 bytes each. This allows each version component to reach
up to 65535. Furthermore, all instances of integer version
types have been replaced with the alias Version::full_t for
a better abstraction. Version literals have been replaced by
Version::fromComponents calls.
Fixes#5827
Previously, the Mumble version was encoded with a uint32
in the network protocol reserving 2 bytes for the major
component and 1 byte for each minor and patch.
The versioning format was changed to include a build
number in the patch field. With a recent update (1.4.274)
the patch field exceeded 255 for the first time and broke
the protocol version.
This commit completely reworks how the version is stored
internally and transfered with the network protocol.
The new version is a uint64 and consists of 4 fields with
2 bytes each. This allows each version component to reach
up to 65535. Furthermore, all instances of integer version
types have been replaced with the alias Version::full_t for
a better abstraction. Version literals have been replaced by
Version::fromComponents calls.
Fixes#5827
This has the advantage of not creating a dependency on the respective
.so/.dll which will be present, even if Tracy support is actually
disabled for the binary. This in turn can cause some issues for
packagers.
Fixed chat log scaling issue introduced by PR #5619
The bug fixed by that commit is still fixed after this PR, but the
regression introduced has been resolved.
Fixes#5818
Fixed chat log scaling issue introduced by PR #5619 (my fault, whoops)
The bug fixed by that commit is still fixed after this PR, but the
regression introduced has been resolved.
Fixes#5818
In 39047d2 a new note was added for
when a user enters minimal view but is not connected to a server.
Incidentally, this caused the new note to appear in the popup menu
appearing as a context menu when using a custom layout, which in theory
would allow a manual toggling of that note's visibility. However, this
is not what we want and thus this commit makes sure that this popup menu
only contains entries for UI elements that we really want to be manually
toggelable.
