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
Every models (like UtilsAdapter for example) owns a pointer of
LRCInstance. So, when the MainApplication is destroyed, the QmlEngine
and all structures owning a pointer of LRCInstance MUST be destroyed
before LRCInstance to avoid any segfault
GitLab: #631
Change-Id: Id30aaca325fe7172188bba468acd73525e62a34a
Qt on Windows defaults to Direct3D rendering backend which causes
flickering and visualy glitchy resizing.
Gitlab: #601
Change-Id: I175d6131aca234f557234a23984e46f94c7d5417
logs from the daemon should not be shown by default, but only in
debug mode, so makes --quiet usable, but only with --debug
Change-Id: Ia7da32e31e034650d184dfae06c9157e13102906
+ Check early for Qt6 and remove module list duplication.
+ Add qrencode-win32 as a submodule. Remove unused libqrencode
submodule(GNU/Linux and macOS use package dependencies).
+ Remove unused ReleaseCompile option.
REQUIRES adjustments to:
- https://jenkins.jami.net/view/clients/job/client-qt-msvc-tests
(JenkinsFile ??)
Gitlab: #601
Change-Id: Ied65c9aaead86009d70f68705f8592950dab2dfa
Dialog in Qt.labs.platform which is used to be native in Qt 5.15
cannnot be accessed in Qt 6.2 for now, use popup dialogs instead
1. Add tittle
2. DropShadow revisit
3. Dim properly
Change-Id: I8804ae0c30e3450c9a800d9a1c3946ff0bf44b46
1. JamiSwitch checked,focused color fixes
2. Avoid MaterialButton dashed line on focus
3. Placeholder text color fixes
Change-Id: I9b04f643e3553fc1f493183eb0e30646818362bd