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
+ 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
* 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
Qt on Windows defaults to Direct3D rendering backend which causes
flickering and visualy glitchy resizing.
Gitlab: #601
Change-Id: I175d6131aca234f557234a23984e46f94c7d5417
- add QtQuickTest, QtTest and googletest support
- create tests folder within cmake hierarchy
- avoid using wildcards in Dockerfile
Change-Id: I81661a86757f01333538908dbc81a0bafae00ab7
- re-introduce a genericized NetworkManager
- isolate update logic into a qml accessible class derived from
NetworkManager
- fix QtWebEngineProcess missing when re-installing over existing
version
- provide a command line option to override the base url
for testing local and remote updates
- clean-up manual update-check UI
Gitlab: #101
Change-Id: I9c8d2badae59ec31cab12d38b8470edf2bcad401
- Introduces a C++/Qml common mechanic for accessing system settings
- Refactors a good chunk of application wide settings management code
- Refactors the onboarding and quit-suppression logic
- Makes a first stab at cleaning the Qml object registration
- Removes some 'ClientWrapper' use
- Fixes some file name spelling errors and inconsistencies
Gitlab: #51
Gitlab: #53
Change-Id: I3dd1085aca72a38827ec004e347bd91106be2bcb
