Bug 392566 - Krita 4.0 and 4.1 pre-alpha Expand/Collapse icon is too small in some places
Summary: Krita 4.0 and 4.1 pre-alpha Expand/Collapse icon is too small in some places
Status: RESOLVED FIXED
Alias: None
Product: krita
Classification: Applications
Component: Usability (show other bugs)
Version: nightly build (please specify the git hash!)
Platform: Debian stable Linux
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-31 14:51 UTC by Ahab Greybeard
Modified: 2018-04-09 11:47 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ahab Greybeard 2018-03-31 14:51:32 UTC
This is present in 4.0.0 and in the latest 4.1.0 (d3f5e19) nightly build, for appimages. It was not present in Krita 3.3.3. This report is based on the use a 1280 x 1024 monitor.

This 'cosmetic' bug would cause confusion for new and inexperienced users.

Throughout Krita, the small black triangle symbol is used to indicate and switch a collapsed/expanded list.
However, there are some places where the triangle is small and indistinct and not easily recognisable for what it is.

e.g: The Edit Brush Settings window, for the list of parameters, for categories such as General, Color, etc.
e.g. The Layers docker blending mode drop down list, for categories such as Favourite, Arithmetic, etc.

There may be other places, not mentioned above.

The only mitigation is to have experience of krita and know what the small black blobs are and how to use them.
Comment 1 Halla Rempt 2018-03-31 14:59:33 UTC
Hm, as far as I know that hasn't changed... And on my (hidpi) plasma5 laptop it's fine. Could you add a screenshot?
Comment 2 Ahab Greybeard 2018-03-31 15:17:17 UTC
Combined screenshots. No rescaling.

https://imgur.com/a/vfqGj

The difference is quite distinct.
Comment 3 Ahab Greybeard 2018-04-09 11:37:19 UTC
It seems to have been fixed in the latest nightly build (aa81a25) in both the places where I reported it as happening.

I don't know if this is by accident or by design.
Comment 4 Halla Rempt 2018-04-09 11:47:56 UTC
Yes -- scott fixed it in 6aea77e2f84a68720f7736b669a1c994dfdc417c, but forgot to add the magic close clause in the commit message.