Quote:
Originally Posted by BetterRed
The highlighting of the current display line when the CV window doesn't have focus is more of an issue for me. I like to use the Tab key to move between 'panels' - if the display line highlight was only shown when CV has KB focus I would know when I landed on it, as it is now I often inadvertently insert Tabs in the text.
BR
|
I played around with this but dropping the highlight when focus is lost just does not work.
Every time a user clicks on a place in Preview to sync with CodeView the highlighting would be lost as Focus goes to Preview so you can not tell where you are after the sync (or that the sync even happened at all if no scrolling is involved). Similar problems happen with Find and Replace as it takes the focus but you can not easily see where you are finding and replacing as the highlight is lost.
I am afraid that is something that too many users rely on (ie - I do!) and so we will not drop current line highlighting when focus is lost as there are many outside windows can can and will interact with the CodeView window but are outside of focus.
Sorry, but your window manager should be making things clear when focus changes by dropping/showing the insertion point cursor. So looking to see when the blinking cursor is in a window is the best way to tell if that window is able to accept keyboard input.
If you have trouble seeing the cursor, please try using Windows Accessibility features to help make it more clear (that does work with macOS Accessibility settings so it should with Window's as well).