Summary: | Window for New document is very big | ||
---|---|---|---|
Product: | [Applications] krita | Reporter: | cheteron <cheteron> |
Component: | General | Assignee: | Krita Bugs <krita-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | amroccapriore, griffinvalley, halla |
Priority: | NOR | ||
Version: | 2.9.11 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Microsoft Windows | ||
Latest Commit: | http://commits.kde.org/krita/a736ca0ad1646b3a4d27dc97134f43bbfcb1a61c | Version Fixed In: | |
Sentry Crash Report: | |||
Attachments: | Big window |
Description
cheteron
2016-02-07 13:53:35 UTC
Created attachment 97066 [details]
Big window
Size of display is 1366x768 Strange that this only happened after 2.9.11... Is the same also happening on the 3.0 pre-alpha? Nope. 3.0 Pre-Alpha have normal window Uninstal and instal Krita again - bug disappear Unfortunately the bug repeats in version 2.9.11 After some experimentation, i find problem. When i take screenshot with Printscreen - window is becoming big, when buffer is empty - window is normal it's the label in the create image from clipboard page that can grow to 300x300 pixels, which pushes the dialog to be too big. We could make it smaller, of course... Git commit 79f0fa0871389e75c8344ec4b374a31cd1c595d1 by Boudewijn Rempt. Committed on 08/02/2016 at 07:45. Pushed by rempt into branch 'master'. Related: bug 75, bug 75 M +20 -23 libs/ui/forms/wdgnewimage.ui M +1 -1 libs/ui/widgets/kis_image_from_clipboard_widget.cpp http://commits.kde.org/krita/79f0fa0871389e75c8344ec4b374a31cd1c595d1 Git commit a736ca0ad1646b3a4d27dc97134f43bbfcb1a61c by Boudewijn Rempt. Committed on 08/02/2016 at 07:33. Pushed by rempt into branch 'rempt-osx-port'. Related: bug 75, bug 75 M +20 -23 libs/ui/forms/wdgnewimage.ui M +1 -1 libs/ui/widgets/kis_image_from_clipboard_widget.cpp http://commits.kde.org/krita/a736ca0ad1646b3a4d27dc97134f43bbfcb1a61c You can explain in more detail? I don't understand what need to do You don't need to do anything, I fixed the bug this morning and it'll be in the next 3.0 build. |