Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
jami-client-qt
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
savoirfairelinux
jami-client-qt
Commits
f25e66aa
Commit
f25e66aa
authored
1 year ago
by
Sébastien Blin
Browse files
Options
Downloads
Patches
Plain Diff
utilsadapter: avoid wrong geometry when getting systray visibility
Change-Id: I05d9770b7198e784356c10164c935b0844cd53b0
parent
79b19aec
Branches
Branches containing commit
Tags
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
src/app/utilsadapter.cpp
+4
-0
4 additions, 0 deletions
src/app/utilsadapter.cpp
with
4 additions
and
0 deletions
src/app/utilsadapter.cpp
+
4
−
0
View file @
f25e66aa
...
...
@@ -829,6 +829,10 @@ UtilsAdapter::isSystemTrayIconVisible()
{
if
(
!
systemTray_
)
return
false
;
// https://bugreports.qt.io/browse/QTBUG-118656
#if defined(Q_OS_LINUX) && !defined(Q_OS_ANDROID)
return
true
;
#endif
return
systemTray_
->
geometry
()
!=
QRect
();
}
...
...
This diff is collapsed.
Click to expand it.
Andreas Traczyk
@atraczyk
mentioned in commit
043a715c
·
11 months ago
mentioned in commit
043a715c
mentioned in commit 043a715c5985f35c66362f0dcf799021ff200dec
Toggle commit list
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment