Bug 386953

Summary: Option to select background color for plugins
Product: [Applications] kate Reporter: avlas <jsardid>
Component: applicationAssignee: KWrite Developers <kwrite-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: normal CC: cullmann, justin.zobel, nate
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:

Description avlas 2017-11-15 17:38:04 UTC
In some themes it's very hard to find out where the hover region of the separator is. Please see:

https://user-images.githubusercontent.com/3875196/32498212-0ba85304-c39d-11e7-9817-c73cecc8204f.png

Having the option to change the background color of plugins would help to solve the problem.
Comment 1 avlas 2017-11-15 19:01:43 UTC
The colorscheme that I use is Adapta-kde. I filled an issue in github about it (https://github.com/PapirusDevelopmentTeam/adapta-kde/issues/25). One of the devs wonders whether the underlying issue here is the stroke of the separator line of Kate plugins. 

Please see https://github.com/PapirusDevelopmentTeam/adapta-kde/issues/25#event-1343642598

Could you please take a look?
Comment 2 avlas 2017-11-15 20:27:35 UTC
This could be the ultimate issue:

https://github.com/PapirusDevelopmentTeam/adapta-kde/issues/25#issuecomment-344716639

Could you please confirm?
Comment 3 Nate Graham 2017-11-15 20:36:35 UTC
Confirmed. This is an issue relating to the use of a different theme, different color scheme, and the decision to turn off borders. Since you've decided on a visual style that doesn't have borders or distinct colors for the different views, there's not much we can do here.

That said, the tab appearance/border issue would be resolved by using native Qt widgets instead of rolling our own, which is tracked by https://bugs.kde.org/show_bug.cgi?id=385520
Comment 4 avlas 2017-11-15 20:41:48 UTC
But isn't it true that the reason why the line (between the scrollbar and kate plugin) is not shown is because the linewidth is set to 0? 

I'm lost :)
Comment 5 Nate Graham 2017-11-15 20:47:27 UTC
Yes, but that's something Qt imposes, not Kate. I think the best way forward is to move toward using a native tab widget instead of a custom one.

But I'll leave this open for Christoph to weigh in.
Comment 6 avlas 2017-11-15 20:48:55 UTC
Ok, thanks for the feedback
Comment 7 Christoph Cullmann 2017-12-20 19:21:25 UTC
The problem with the native tab widget is that it doesn't allow us to customize it in a way we need for the LRU like tabbing.

Besides I am a bit confused: We talk here about the issue that the splitter handle is not easily to catch, or? If some border/line size setting would solve that, we can do this with our widget, too.
Comment 8 avlas 2017-12-23 07:10:30 UTC
> If some border/line size setting would solve that, we can do this with our widget, too.

If that means a line width different than 0, then I think that would solve the issue, yes.
Comment 9 Justin Zobel 2020-10-27 03:21:32 UTC
Have tested on stock Adapta-KDE Global theme and can see the position to grab to resize.

Avlas, can you please confirm if this is still an issue for you?
Comment 10 Bug Janitor Service 2020-11-11 04:33:45 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 11 Bug Janitor Service 2020-11-26 04:33:59 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!