Bug 280638 - not very clear which view is active when using splitted views
Summary: not very clear which view is active when using splitted views
Status: RESOLVED DUPLICATE of bug 158379
Alias: None
Product: kate
Classification: Applications
Component: application (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-23 11:10 UTC by Dmitry Suzdalev
Modified: 2012-10-28 19:46 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
screenshot (102.56 KB, image/png)
2011-08-23 11:11 UTC, Dmitry Suzdalev
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dmitry Suzdalev 2011-08-23 11:10:32 UTC
Version:           unspecified (using KDE 4.7.0) 
OS:                Linux

Recently I started to actively use splitted views and I ran into issue that it is really hard to tell which view is currently active.

If I do some non-editing activity and then return to kate, I have to do a couple of F8's to switch between views so that I can actually find out what view is active by jumping cursor here and there.

Not really convenient :)

Please take a look at attached screenshot and try to QUICKLY guess what view is active? :)

Reproducible: Didn't try

Steps to Reproduce:
Open Kate, split views

Actual Results:  
It is really hard to tell which view is active by just looking at window

Expected Results:  
There's some kind of color/brightness/whatever indication which makes it possible to clearly identify the active view

OS: Linux (i686) release 3.0-ARCH
Compiler: gcc
Kate: 3.7.0

NOTE: using Kate in GNOME environment with qt's gtk theme
Comment 1 Dmitry Suzdalev 2011-08-23 11:11:01 UTC
Created attachment 63068 [details]
screenshot
Comment 2 Dmitry Suzdalev 2011-08-23 11:12:38 UTC
Also wanted to note that bug report form didn't contain my kate version (3.7.0) in version selection combobox - there were 3.0 and 4.0, but nothing like 3.7.0...
Comment 3 Christoph Cullmann 2012-10-28 19:46:42 UTC

*** This bug has been marked as a duplicate of bug 158379 ***