#967 Add property : Highlight line not shown when inactive

Won't_Implement
closed
SciTE (235)
3
2013-04-12
2013-01-03
No

In regard of "Highlight line not shown when window inactive - ID: 3592730" < https://sourceforge.net/tracker/index.php?func=detail&aid=3592730&group_id=2439&atid=352439 >, is it possible to add property to enable this feature form SciTE?

Discussion

  • Neil Hodgson

    Neil Hodgson - 2013-01-03

    Its a horrible misfeature, making it more difficult to tell active from inactive windows. I won't be working on it.

     
  • Neil Hodgson

    Neil Hodgson - 2013-01-03
    • assigned_to: nobody --> nyamatongwe
    • priority: 5 --> 3
    • milestone: --> Won't_Implement
     
  • Jérôme LAFORGE

    IMHO, this behavior can be useful.
    Into my default config of my SciTE, I have enabled "caret.line.back". When I want replace some words (and not all words) with "replace by" dialog box, the focus is took by the "replace by" box. So the caret line back is not highlight (cause the main window lost its focus).
    It's more difficult to find where the caret is positioned to determine whether I can replace this word or not.

    Maybe, if the caret.line.back is set, then the line back is always visible (w/ or w/o focus).
    Will you accept kind of behavior? If so, I can propose a simple patch.

     
  • Neil Hodgson

    Neil Hodgson - 2013-01-03

    That would be even worse since it forces this poor behaviour on everyone already using caret.line.back.

     
  • Jérôme LAFORGE

    Ok, could you at least update the IFace Table of SciTE that allows to call this feature from lua for the persons whom, like me, appreciate this "poor" behavior.

     
  • Jérôme LAFORGE

    Ok, could you at least update the IFace Table of SciTE that allows to call this feature from lua for the persons whom, like me, appreciate this "poor" behavior.

     
  • Neil Hodgson

    Neil Hodgson - 2013-04-12
    • status: open --> closed
     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks