Bug 410793

Summary: Settings dialog is too high for very space constrained screens
Product: [Applications] krita Reporter: Galaxy Silver <argentinecosmos>
Component: GeneralAssignee: Krita Bugs <krita-bugs-null>
Status: RESOLVED FIXED    
Severity: minor CC: halla, motnitsuj, scottpetrovic, Zaji
Priority: NOR    
Version: 4.2.5   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed In:
Attachments: Image is "OK" and "Cancel" buttons of Configure Krita window being blocked by Windows taskbar.
attachment-32722-0.html

Description Galaxy Silver 2019-08-10 17:16:52 UTC
Created attachment 122048 [details]
Image is "OK" and "Cancel" buttons of Configure Krita window being blocked by Windows taskbar.

SUMMARY
The "OK" and "Cancel" buttons of the preferences/Configure Krita window are too low, they're off screen, thus it's not possible to press them unless I change the taskbar setting so it's on other side and not on bottom.

STEPS TO REPRODUCE
1. Go to Settings
2. Choose Configure Krita...
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 10 Home Single Language
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Halla Rempt 2019-08-10 17:49:42 UTC
Looks like your screen's resolution is too low, or your display scaling set too high. What is the resolution of your screen and what is the display scaling and font scaling set to?
Comment 2 Galaxy Silver 2019-08-10 18:16:56 UTC
   My screen resolution is 1366 x 768, and I don't know where to check my
   font and display scaling, unless it's a setting on Krita and not
   Windows?

   On Aug 11, 2019 12:49 AM, Boudewijn Rempt <bugzilla_noreply@kde.org>
   wrote:

     https://bugs.kde.org/show_bug.cgi?id=410793

     Boudewijn Rempt <boud@valdyas.org> changed:

     What |Removed |Added
     ----------------------------------------------------------------------------
     Severity|normal |minor
     CC| |boud@valdyas.org
     Summary|Confirm Buttons are Blocked |Settings dialog is too high
     |by Taskbar |for very space constrained
     | |screens

     --- Comment #1 from Boudewijn Rempt <boud@valdyas.org> ---
     Looks like your screen's resolution is too low, or your display
     scaling set too
     high. What is the resolution of your screen and what is the
     display scaling and
     font scaling set to?

     --
     You are receiving this mail because:
     You reported the bug.
Comment 3 Halla Rempt 2019-08-11 10:05:33 UTC
Scaling a setting in Windows. Open the See for instance https://www.lifewire.com/using-windows-10-display-scaling-4587328 -- but that's not relevant. Your screen's resolution just is really, really low, and it's really hard to fit in everything in such a small area. But I guess we should try...
Comment 4 Halla Rempt 2019-08-11 11:23:50 UTC
*** Bug 410808 has been marked as a duplicate of this bug. ***
Comment 5 Scott Petrovic 2019-08-11 12:40:36 UTC
I think this window got too big when the HDR settings area was added to the display part. I just checked out a nightly build on my Surface Pro. Between the HDR area and all the text warning stuff we have with ANGLE and OpenGL, that is pushing this area further down so it doesn't fit on a 1366x768 monitor.

We are probably going to have to break this Display area into multiple tabs like we do with the General section
Comment 6 Halla Rempt 2019-08-12 07:08:44 UTC
Git commit 14d3ca274c700d369b7f3094e35dcc4a45cfc509 by Boudewijn Rempt.
Committed on 12/08/2019 at 07:08.
Pushed by rempt into branch 'master'.

Split the display settings page in tabs

M  +545  -458  libs/ui/forms/wdgdisplaysettings.ui

https://invent.kde.org/kde/krita/commit/14d3ca274c700d369b7f3094e35dcc4a45cfc509
Comment 7 Galaxy Silver 2019-08-12 14:26:27 UTC
Created attachment 122085 [details]
attachment-32722-0.html

 Hello! I appreciate that the both of you are replying to my bug, but I don't know what can I do with the latest info/link you provided to me? Should I change the app's code? I mean, I'm fine with the buttons being blocked rather than ruining the whole app because I'm not tech-savvy enough, I never changed or copied and pasted code to Krita before, despite it being open source.
(Also, yes, the display scaling isn't helping, mine is in the lowest setting, if you're wondering...)    On Monday, August 12, 2019, 02:08:48 PM GMT+7, Boudewijn Rempt <bugzilla_noreply@kde.org> wrote:  
 
 https://bugs.kde.org/show_bug.cgi?id=410793

Boudewijn Rempt <boud@valdyas.org> changed:

          What    |Removed                    |Added
----------------------------------------------------------------------------
      Latest Commit|                            |https://invent.kde.org/kde/
                  |                            |krita/commit/14d3ca274c700d
                  |                            |369b7f3094e35dcc4a45cfc509
            Status|CONFIRMED                  |RESOLVED
        Resolution|---                        |FIXED

--- Comment #6 from Boudewijn Rempt <boud@valdyas.org> ---
Git commit 14d3ca274c700d369b7f3094e35dcc4a45cfc509 by Boudewijn Rempt.
Committed on 12/08/2019 at 07:08.
Pushed by rempt into branch 'master'.

Split the display settings page in tabs

M  +545  -458  libs/ui/forms/wdgdisplaysettings.ui

https://invent.kde.org/kde/krita/commit/14d3ca274c700d369b7f3094e35dcc4a45cfc509
Comment 8 Halla Rempt 2019-08-12 14:56:22 UTC
No, you should either use a nightly build, or wait until this change makes it into the next release -- end of this month, actually. Nightlies are here: https://binary-factory.kde.org/job/Krita_Nightly_Windows_Build/
Comment 9 Halla Rempt 2019-08-15 07:53:48 UTC
Git commit 4908bde943606ae8e5355a4520360df459ded15b by Boudewijn Rempt.
Committed on 15/08/2019 at 07:44.
Pushed by rempt into branch 'krita/4.2'.

Split the display settings page in tabs

M  +545  -458  libs/ui/forms/wdgdisplaysettings.ui

https://invent.kde.org/kde/krita/commit/4908bde943606ae8e5355a4520360df459ded15b
Comment 10 Halla Rempt 2019-08-26 12:27:55 UTC
*** Bug 411281 has been marked as a duplicate of this bug. ***