[kate] [Bug 416078] Broken UI since 4d09f48

2020-01-26 Thread Christoph Cullmann
https://bugs.kde.org/show_bug.cgi?id=416078 --- Comment #19 from Christoph Cullmann --- Should now be fixed in 19.12 branch + master -- You are receiving this mail because: You are watching all bug changes.

[kate] [Bug 416078] Broken UI since 4d09f48

2020-01-26 Thread Christoph Cullmann
https://bugs.kde.org/show_bug.cgi?id=416078 --- Comment #16 from Christoph Cullmann --- Seems that the pass-through is a bad idea for unices :/ Let's just enable that at the moment for Windows, there it seems to properly work. -- You are receiving this mail because: You are watching all bug cha

[kate] [Bug 416078] Broken UI since 4d09f48

2020-01-26 Thread Christoph Cullmann
https://bugs.kde.org/show_bug.cgi?id=416078 Christoph Cullmann changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|---

[kate] [Bug 416078] Broken UI since 4d09f48

2020-01-26 Thread Christoph Cullmann
https://bugs.kde.org/show_bug.cgi?id=416078 Christoph Cullmann changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://commits.kde.org/kat

[kate] [Bug 416078] Broken UI since 4d09f48

2020-01-22 Thread Christoph Cullmann
https://bugs.kde.org/show_bug.cgi?id=416078 --- Comment #15 from Christoph Cullmann --- No idea. I tried a bit more with the Qt flags, but without QCoreApplication::setAttribute(Qt::AA_EnableHighDpiScaling, true); scaling is problematic in other cases :/ -- You are receiving this mail because:

[kate] [Bug 416078] Broken UI since 4d09f48

2020-01-22 Thread Christophe Giboudeaux
https://bugs.kde.org/show_bug.cgi?id=416078 --- Comment #14 from Christophe Giboudeaux --- Now that plasma-workspace was updated to also set QT_AUTO_SCREEN_SCALE_FACTOR to 0 with Qt 5.14, I don't know what to do with this report. -- You are receiving this mail because: You are watching all bug

[kate] [Bug 416078] Broken UI since 4d09f48

2020-01-10 Thread Christoph Cullmann
https://bugs.kde.org/show_bug.cgi?id=416078 --- Comment #13 from Christoph Cullmann --- Hmm, I guess I need to test this more extensive at home, at least in our company our UI guy has the same issue at the moment with the 5.14 update and our internal stuff. Some things look blurry now. -- You a

[kate] [Bug 416078] Broken UI since 4d09f48

2020-01-10 Thread Christoph Cullmann
https://bugs.kde.org/show_bug.cgi?id=416078 --- Comment #12 from Christoph Cullmann --- I think QCoreApplication::setAttribute(Qt::AA_EnableHighDpiScaling, true); with QGuiApplication::setHighDpiScaleFactorRoundingPolicy(Qt::HighDpiScaleFactorRoundingPolicy::PassThrough); leads to doom. Shal

[kate] [Bug 416078] Broken UI since 4d09f48

2020-01-10 Thread Christoph Cullmann
https://bugs.kde.org/show_bug.cgi?id=416078 --- Comment #11 from Christoph Cullmann --- See more complaints about this in bug 373232. Konsole doesn't set setHighDpiScaleFactorRoundingPolicy yet, just the usual QCoreApplication::setAttribute(Qt::AA_UseHighDpiPixmaps, true); QCoreApplica

[kate] [Bug 416078] Broken UI since 4d09f48

2020-01-10 Thread Christoph Cullmann
https://bugs.kde.org/show_bug.cgi?id=416078 --- Comment #10 from Christoph Cullmann --- If we can fix that in kate/kwrite/... code, I am happy to do so, but what is actually the correct sequence of stuff to setup hidpi support? So far, it seemed to be: /** * enable high dpi support

[kate] [Bug 416078] Broken UI since 4d09f48

2020-01-10 Thread Christophe Giboudeaux
https://bugs.kde.org/show_bug.cgi?id=416078 Christophe Giboudeaux changed: What|Removed |Added CC||fa...@kde.org --- Comment #9 from Chris

[kate] [Bug 416078] Broken UI since 4d09f48

2020-01-10 Thread Christoph Cullmann
https://bugs.kde.org/show_bug.cgi?id=416078 --- Comment #8 from Christoph Cullmann --- I don't actually understand why this change should trigger that :/ -- You are receiving this mail because: You are watching all bug changes.

[kate] [Bug 416078] Broken UI since 4d09f48

2020-01-10 Thread Christophe Giboudeaux
https://bugs.kde.org/show_bug.cgi?id=416078 --- Comment #7 from Christophe Giboudeaux --- Playing with the "global scale" settings in systemsettings/display & monitor "fixes" the broken UI elements but the font are (obviously) way too big -- You are receiving this mail because: You are watching

[kate] [Bug 416078] Broken UI since 4d09f48

2020-01-10 Thread Christoph Cullmann
https://bugs.kde.org/show_bug.cgi?id=416078 --- Comment #6 from Christoph Cullmann --- :( This is all crap I use at home 1.5 scaling with dual-head and I thought it works even after this patch, need to re-try that, not that I have actually used a Qt < 5.14 :/ -- You are receiving this mail bec

[kate] [Bug 416078] Broken UI since 4d09f48

2020-01-10 Thread Christophe Giboudeaux
https://bugs.kde.org/show_bug.cgi?id=416078 --- Comment #5 from Christophe Giboudeaux --- Running kwrite with QT_AUTO_SCREEN_SCALE_FACTOR=0 helps btw. I'm using a dual monitor setup but didn't change the scaling. -- You are receiving this mail because: You are watching all bug changes.

[kate] [Bug 416078] Broken UI since 4d09f48

2020-01-10 Thread Christoph Cullmann
https://bugs.kde.org/show_bug.cgi?id=416078 --- Comment #4 from Christoph Cullmann --- What is your screen scale factor? -- You are receiving this mail because: You are watching all bug changes.

[kate] [Bug 416078] Broken UI since 4d09f48

2020-01-10 Thread Christoph Cullmann
https://bugs.kde.org/show_bug.cgi?id=416078 Christoph Cullmann changed: What|Removed |Added CC||cullm...@kde.org --- Comment #3 from Chris

[kate] [Bug 416078] Broken UI since 4d09f48

2020-01-10 Thread Christophe Giboudeaux
https://bugs.kde.org/show_bug.cgi?id=416078 Christophe Giboudeaux changed: What|Removed |Added Summary|Broken UI since 68a2de71|Broken UI since 4d09f48 --- Comment #2