The --enable-gnutls option was added to the bootstrap command on
Debian-based distributions in jami-project commit 46bdda4 in 2017,
because at the time they built GnuTLS without HeartBeat support. This is
no longer true on the more modern versions of Debian and Ubuntu that we
currently support.
GitLab: #1998
Change-Id: I593682e0f8aeb2015a109980840f373b1306670a
The debian installer requires libavcodec60 as a dependency, which is
already included in linuxmint through libavcodec-extra60, creating a
package conflict.
Changes to fix this :
- also accept libavcodec-extra as a dependency as it includes libavcodec
GitLab: #1937
Change-Id: Ia3ab39e6d8bd233414c607ab70fd70af629595b0
We need the EXCLUDE_FROM_ALL argument to prevent Hunspell's headers from
being installed by Jami's "install" make target.
GitLab: #1997
Change-Id: Ie60c6f4dc8dc8b33fbccb95d667b4b2eafefecb6
The Hunspell library was added to the project as a git submodule in
commit 2a72da5, but some packaging scripts were not updated accordingly.
GitLab: #1997
Change-Id: I5e6079fc23aeecfba2076067ecf5c4ed1f5a591a
The default value was set to "None" in appsettingsmanager.h but the rest
of the code assumes that the default is "NONE" (see commit 2a72da5).
GitLab: #1997
Change-Id: Ifeac3399b1b48bad0863a1b7da9228df43f73b76
Add a setting to allow the app to be raised to foreground when called.
Some special setups like virtual machines can prevent this behaviour.
GitLab: #2004
Change-Id: I0f6ea442f6abe88109e81933b731f81d10bd6c8f
Delete the default settings in the settings file so that only user
defined ones are stored locally.
Previously, we stored every value in the settings file. This created a problem where we could not modify a default value as we had no way of knowing if it was user defined or not.
This patch allow us to know that if a value was in the file, it's that it was different from the default.
GitLab: #2000
Change-Id: I7d5154b258c2ca97a1976dc006a70db0d5fe0b31
Implement a first version of the spellcheck for linux that use the
systemwide installed dictionaries.
GitLab: #1997
Change-Id: I7158e6c61061e7d0a7fe651069247227bbe399a4
Set the preview of the windows shared at one FPS and allows to set
custom FPS count to a window.
GitLab: #1242
Change-Id: Ia189500267de18d0809d8d4db781c7015623fa8c
When a new device is connected/disconnected update audio devices list in
the media settings.
This commit also bumps jami-daemon to support DevicesChanged events on
Windows.
Gitlab: #689
Gitlab: #1878
Change-Id: Ibb607939897853794fdbd09eab72f378257d458c
Brings in some build fixes. Also prevents applying the qmsetup patch
on Windows, and calls build-windows.py --init with the qt parameter
which is required if when using Qt installed in a non-standard location.
Change-Id: I40facbdc93289792130a15b0f4151f78137bc1ef
This commit adds a patch for QWindowKit to ensure that it always
installs its dependency QMSetup in a directory where CMake will be able
to find it. This makes the previous QWindowKit patch unnecessary and
fixes a build issue when packaging Jami on Debian and Ubuntu that
started occurring when QWindowKit was updated in commit 6b70ffc.
GitLab: #1976
Change-Id: I5f23fcbb612aa6d0eb0e77e9a5a006b24a5af082
New device identifier is not recognized.\nPlease follow above instruction. → Unrecognized new device identifier. Please follow the instructions above.
Change-Id: I75a1f89d738629eff031bdd3258435d7b72a4fce
The attempted fix in commit 65d3bef was based on the incorrect
assumption that md4c systematically fails to detect links that contain
at least one +, - or _. This commit removes the postprocessing step
added in 65d3bef and instead patches md4c to directly fix its link
recognition algorithm.
GitLab: #1903
GitLab: #1964
Change-Id: Ic1d6302e3250390af66611a16715a6397578abb5
The submenus are no longer created dynamically, so bindings are
required for positioning.
Gitlab: #1965
Change-Id: Idc2fe77f00ff9b2124f0bad4cc1a8160cd01bf04
The bug is caused by the computation of `elementWidth` when the list
model length is zero and `showWindows` is true. In this case, division
by zero causes the `elementWidth` to have the value `Infinity`. We
presume that at this point, the component's rendering may take a
while.
This commit refactors the layout to use a GridLayout and a more stable
approach to displaying the delegate components, while removing a
potentially harmful Qt bug [1] workaround.
[1]: https://bugreports.qt.io/browse/QTBUG-110323
Gitlab: #1242
Change-Id: Ib3df1568fdbcdd799fcdcf0b39cb87e3de50dc42
