Bug 362525

Summary:	Advanced color selector configuration dialog unusable on HiDPI
Product:	[Applications] krita	Reporter:	Ilya V. Portnov <portnov>
Component:	Color Selectors	Assignee:	Krita Bugs <krita-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	halla
Priority:	NOR
Version First Reported In:	3.0 Beta
Target Milestone:	---
Platform:	Kubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	Shaders page Image colors page Colors history page

Description Ilya V. Portnov 2016-05-01 06:17:54 UTC

I have a laptop with 2880x1620 screen resolution, and configuration dialog for Advanced color selector is almost unusable here. Will attach screenshots (sorry for russian l10n, i think you will understand which pages of dialog these are).
This is krita3-testing from lime PPA on newly-installed Kubuntu 16.04.

Reproducible: Always

Comment 1 Ilya V. Portnov 2016-05-01 06:20:27 UTC

Created attachment 98718 [details]
Shaders page

Comment 2 Ilya V. Portnov 2016-05-01 06:21:03 UTC

Created attachment 98719 [details]
Image colors page

Comment 3 Ilya V. Portnov 2016-05-01 06:21:39 UTC

Created attachment 98720 [details]
Colors history page

Comment 4 Halla Rempt 2016-05-04 06:25:58 UTC

Hi Ilya,

Could you check if Dmitry's commit aefcb2677e1d04f63bcedde8a75e01a5ef52a437 fixes the issue?

Comment 5 Ilya V. Portnov 2016-05-04 14:59:22 UTC

I currently do not have krita building environment on the laptop where i have hidpi display. Will this commit be included in one of next lime ppa build or appimages?

Comment 6 Halla Rempt 2016-05-04 16:12:05 UTC

Yes, I might be making them tomorrow.

Comment 7 Ilya V. Portnov 2016-05-05 14:55:46 UTC

Advanced color selector configuration dialog became much better with today update from lime ppa. Thanks!

I also have (maybe related) similar problem with brush settings dialog on hidpi. Should I create separate ticket for that?

Comment 8 Halla Rempt 2016-05-06 08:07:55 UTC

Yes.

Comment 9 Ilya V. Portnov 2016-05-08 16:44:46 UTC

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

As for this bug, i think we should mark it as fixed.