- 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
Move installTranslator into the settings manager and add a settings
in the SystemSettings to be able to dynamically change the language
of jami-qt.
https://git.jami.net/savoirfairelinux/jami-project/-/issues/1342
Change-Id: I4f720fa50d5e313356dbdf1b8acb4e98d74401e4
+ Reduce listview caching' size by 50%
+ use sourceSize to compress images and speedup loading
+ use autoTransform: true to rotate images when needed
Change-Id: Idf1babdc73f43aa6a79b89428c25c5d06856c0ef
GitLab: #649
The running instance may be ephemeral and end up discarded after being
checked by InstanceManager. In this case, we shouldn't initialize large
components.
Gitlab: #654
Change-Id: I30c7dcdba6a56ab3a1a84a9efd3424e266b6f6ce
Qt6 allows us to set the RHI backend, however QQuickWidget is only
supported when using OpenGL. QWebEngineView instantiation uses
QQuickWidget and isn't required as we wish to use the previewengine
in a headless mode. So it can just be based on QWebEnginePage.
Change-Id: If05ca5c89272704b54c29318803c8773984b087c
Save virtual desktop geometry and window visibility state settings
and set them for the application window when loading.
Gitlab: #604
Change-Id: I053716d9c7b5d23e1bd7f33a1c41aedefb6cf9c8
The comment was incorrect (it check the fingerprint, not the alias)
and the condition was duplicated
Change-Id: I2b3a21de64797dc90abaaa452645d7b0e6183ac1
* src/main.cpp (main): unset QT_STYLE_OVERRIDE. Some distros, like
Zorin OS, set QT_STYLE_OVERRIDE to force a particular Qt style.
This has been fine with Qt5 even when using our own Qt package
which may not have that style/theme available. However, with Qt6,
attempting to override to a nonexistent style seems to result in the
main window simply not showing. So here we unset this variable, also
because jami-qt currently has the Material style hard-coded anyway.
https://bugreports.qt.io/browse/QTBUG-99889
Change-Id: Ic261b46baf79cf36491578ff969b398b95363c94
Logic for fullscreen/windowed mode switching is scattered within
the main ApplicationWindow and other components. Ideally,
components that need to transition to fullscreen, can make a dumb
request to module in charge of making the necessary checks and
carrying out the mode change.
This patch introduces the LayoutManager used to isolate this logic.
Change-Id: I0e5b932617d2b88eda1533f25a5d55fc1c66c438
Remove all references to appWindow.isFullScreen and uses visibility
Store latest state to keep previous states when passing the call
in fullscreen or a media player. Fix also fullscreen's transition
on media messages
Change-Id: I1b141fc052aa607561275faf231504f48b3c49b8
Superposing a MouseArea and a hover in a child
component may cause focus problems.
This replaces MouseArea for a HoverHandler
in the participant moderator menu.
Change-Id: Ic4eb763c79f04198d3a2a2f24636fb2a09dca172
GitLab: #601
remove useless isFullscreen (visibility already stores this and
it's not possible to go from fullscreen to minimized anyway).
Also --minimized was ignored
GitLab: #413
Change-Id: I610f17ce7ae5b2852aae5b40dc504174fa657c2d
