Bug 396872 - can not see dock panel settings
Summary: can not see dock panel settings
Status: RESOLVED FIXED
Alias: None
Product: lattedock
Classification: Plasma
Component: application (show other bugs)
Version: 0.8.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Michail Vourlakos
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-07-26 11:02 UTC by Anders Honore
Modified: 2018-07-26 23:12 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
screenshot of the too narrow settings window (789.05 KB, image/jpeg)
2018-07-26 11:08 UTC, Anders Honore
Details
screenshot of font dpi after change (532.54 KB, image/jpeg)
2018-07-26 11:28 UTC, Anders Honore
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Anders Honore 2018-07-26 11:02:12 UTC
Dock panel settings show up as a tiny bar for me. I can just about gleam the buttons there, but it is too narrow to do anything.
Comment 1 Michail Vourlakos 2018-07-26 11:06:22 UTC
1. screenshot?
2. font dpi setting?
3. Screen resolution?
4. Screen scaling factor?
Comment 2 Anders Honore 2018-07-26 11:08:33 UTC
Created attachment 114141 [details]
screenshot of the too narrow settings window
Comment 3 Anders Honore 2018-07-26 11:09:39 UTC
dpi is 144, scaling factor is 1.5. resolution is 3200x1800
Comment 4 Michail Vourlakos 2018-07-26 11:14:43 UTC
(In reply to Anders Honore from comment #2)
> Created attachment 114141 [details]
> screenshot of the too narrow settings window

the width for dock settings window is calculated through:
34 * theme.defaultFont.pixelSize

in your system the font you are using for some reason returns zero...

What font are you using? Can you make a screenshot for Fonts at plasma systemsettings? If you use another font and re-login to plasma the problem remains?
Comment 5 Anders Honore 2018-07-26 11:28:05 UTC
Created attachment 114142 [details]
screenshot of font dpi after change

After changing from PT sans to sans serif and logging out and in again
Comment 6 Michail Vourlakos 2018-07-26 11:33:28 UTC
can you upload your layout please?
Comment 7 Anders Honore 2018-07-26 11:46:28 UTC
you mean config file? I am quite new to Latte - what is the path?
Comment 8 Michail Vourlakos 2018-07-26 11:53:38 UTC
(In reply to Anders Honore from comment #7)
> you mean config file? I am quite new to Latte - what is the path?

1. close Latte
2. all your latte layout files are located at: 
~/.config/latte

There is also a Latte Layouts editor you can export them if you want, you can access it with shortcut Meta+W or Meta+E
Comment 9 Michail Vourlakos 2018-07-26 23:07:22 UTC
Git commit f2172562c095932c3b4ae6892a5ad95bc4cb6869 by Michail Vourlakos.
Committed on 26/07/2018 at 23:06.
Pushed by mvourlakos into branch 'master'.

dont allow settings window width to be very small

--to make things even more robust the dock settings
window width is made a portion of the dock settings
window height. The code was also checked in order to not
create any bindings loops

M  +1    -1    shell/package/contents/configuration/LatteDockConfiguration.qml
M  +1    -1    shell/package/contents/configuration/LatteDockSecondaryConfiguration.qml

https://commits.kde.org/latte-dock/f2172562c095932c3b4ae6892a5ad95bc4cb6869
Comment 10 Michail Vourlakos 2018-07-26 23:10:56 UTC
Git commit f700ac4f2ca9d96be405b27c3be8920aace1d39a by Michail Vourlakos.
Committed on 26/07/2018 at 23:10.
Pushed by mvourlakos into branch 'v0.8'.

dont allow settings window width to be very small

--to make things even more robust the dock settings
window width is made a portion of the dock settings
window height. The code was also checked in order to not
create any bindings loops

M  +1    -1    shell/package/contents/configuration/LatteDockConfiguration.qml
M  +1    -1    shell/package/contents/configuration/LatteDockSecondaryConfiguration.qml

https://commits.kde.org/latte-dock/f700ac4f2ca9d96be405b27c3be8920aace1d39a
Comment 11 Michail Vourlakos 2018-07-26 23:12:13 UTC
(In reply to Anders Honore from comment #0)

I made also a commit to prevent this from happening but it will be available from v0.8.1