Bug 223057

Summary:	Wish - Add to Settings -> Configure Kompare the ability to make the current position highlight contrast clearer, or even completely configurable.
Product:	[Applications] kompare	Reporter:	Graham Seale <GTrax99>
Component:	general	Assignee:	Kompare developers <kompare-devel>
Status:	RESOLVED WORKSFORME
Severity:	normal
Priority:	NOR
Version:	4.0.0
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Graham Seale 2010-01-17 01:14:34 UTC

Version:           4.0.0 (using KDE 4.3.2)
Compiler:          gcc 4.4.1 
OS:                Linux
Installed from:    Ubuntu Packages

The visual difference in shading, to highlight where we are among the default pink (changed) regions, is just not strong enough. Once the texts have scrolled away from  the start,  I find myself scrolling back and forward, hunting for the place with the subtle bright-up in pink. This is one feature that badly needs to be somewhat user configurable.

Related issues:
Google "color blindness tests" images to appreciate why some of the pinks and greens chosen in the defaut setup can be problematic. One good aid to checking the choice is to temporarily display in monochrome.

In general, avoid certain colours adjacent that will clash, and appear to "vibrate" (e.g. primary saturated blue against red). Certain others present a maximum contrast without clash (eg, slightly darkened magenta on pale yellow).

Consider too, optical illusion effects from horizontal converging lines (Kompare seems OK on this)
___________

At the least, improved ability to see where we are in the file is only a small addition, but will make a very big difference to some of us.

Comment 1 Andrew Crouthamel 2018-11-02 22:54:01 UTC

Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!

Comment 2 Andrew Crouthamel 2018-11-16 02:48:22 UTC

Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version?

Thank you for helping us make KDE software even better for everyone!

Comment 3 Justin Zobel 2022-12-08 23:51:16 UTC

Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!

Comment 4 Bug Janitor Service 2022-12-23 05:22:52 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 5 Bug Janitor Service 2023-01-07 05:25:39 UTC

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!