These aren't really needed and seem to be stale builds after
building with scripts, and retrigger in vs.
Change-Id: I5c60efc0018893195dd3549fb2df52b907da5230
+ Removes the console log management code which is present in jamid
using https://review.jami.net/c/jami-daemon/+/21251.
+ Adds back file logging which has been partially broken since
the log monitoring feature was added.
Change-Id: I07681b1c8d48702678596fbc302c21f87284b6e4
Set minimum macOS version for sparkle updater to 10.14. The same
minimum version is required by qt 6. So only users with macOS 10.14
or higher will be offered to update jami to qt version on macOS.
Change-Id: I58b081a2a042db118d06724f7a6e9359feefb59c
We've had reports of missing vulkan dependencies on fresh Windows
10 installs. Until this has been investigated, we should keep the
default rendering backend at the cost of some flicker.
Change-Id: Idaab06ff80d7841231270a207cceb134f8d790b0
participants contains all the swarm members, including ourself.
To show notifications for conversations we should use the avatar
for this conversation and its title
Change-Id: I82f4c34f94c6313395361cfd337562f4e3c927c4
Removes the rendermanager and framewrapper objects along with any
QQuickPaintedItem-based QML render widget classes. This simplifies
the video widget stack implementation.
The new mechanism uses the VideoOutput component of QtMultimedia.
By accessing the VideoOutput's QVideoSink object, we update the
mapped buffer data of a sink's QVideoFrame when new frames are
published. Updates to frames and component sink subscriptions are
managed by a new class called VideoProvider.
Gitlab: #500
Also https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/536
Change-Id: I2391a32294922ea435ab80ac1f876c004ff6c21e
Horizontal view show components horizontally in a vertical layout.
So, the labels were inverted
Change-Id: Iaecfa923ef0a2eb1ec810ab0436dddd4f4ea73e5
GitLab: #571
- fix translations path
- generate .lproj folders for supported languages to be recognized by
QLocale. https://bugreports.qt.io/browse/QTBUG-72491
Gitlab: #578
Change-Id: Ic4c3b74c654a1c00de71c31c9debe397990870f7
With hardened runtime app crashes in sws_scale when converting pixel
formats. Unsigned executable memory entitlement fix the crash.
Change-Id: Ia6e8cd0b1ff9537343991f730d0ed63384d17c2d
This adds a windows sharing button in addition to the sharing options.
This button is only available for linux systems and must be enabled
for others (MacOS, Windows) once their windows sharing are functional.
Change-Id: If378a23bc504fd3813382e84a41d914448707616
GitLab: #668
Sometimes deploy failed with qmlimportscanner error. For better
control macdeployqt will be called manually for release
builds.
Gitlab: #578
Change-Id: Ic3a781cb4680499bbb7e479e31764f3f35e29800
We do not need to verify if an app instance already running
on macOS, because it is done by default. Moreover, it causes a crash
on the macOS app with enabled hardened runtime.
Gitlab: #578
Change-Id: Ic8aa6a136d394372890ed4010f4a3c7ffa8e9233
+ Refactors some window management logic in LayoutManagar.qml.
+ Refactors app start to support both a minimized start and a start
URI. The start URI should force visibility.
+ StartMinimized now starts the application in a closed-to-tray
state, instead of a minimized state.
+ The close-to-tray feature now saves the previous windowed state.
+ InstanceManager handles URI transfer to secondary instances.
This commit does not implement URI handling. The original
implementation supported only calls via a user infohash as the URI
parameter. A new and flexible protocol should be defined to support
multiple Jami features.
Gitlab: #655
Change-Id: I2c47028930e4e9d7ccca94d9362545df14b98160
To coordinate the MSI installer with Jami's close-to-tray feature,
a custom action was used to kill QtWebEngineProcess and Jami, prior
to the file installation step. The close-to-tray feature makes it
so the only way to terminate the app is via the systray context
menu.
This patch harnesses the IPC mechanism used by the run-guard, and
adds a command-line option('--term') used to signal the secondary
process and provoke graceful termination.
The benefits are:
- the app can save data before closing
- system tray icons aren't left dangling after updates
- QtWebEngineProcess is guaranteed to be terminated during install
Gitlab: #654
Gitlab: #543
Change-Id: I79421eeab49c9ec0826010af99a364471bb81d1a
Components.onCompleted is not called after engine_->retranslate(),
causing the menu to not change. Doing a model for 4 buttons is
overkill, so just do the menu.
https://git.jami.net/savoirfairelinux/jami-project/-/issues/1342
Change-Id: I412230cc2152948666e37fe11824ee347bf55644