Open HamRusTal opened 5 years ago
Thanks for the suggestion. I will see if I can find out how the method separator worked. It might be based off outlining information -- which would make an implementation somewhat easier than trying to do syntax parsing on the buffer content itself (which, of course gets us into language-specific code).
Actually, there's an option for VB and C# in Tools/Options called "Show procedure line separators". It's on by default for VB, but off for C#. @HamRusTal Does that do what you want?
there's an option for VB and C# in Tools/Options called "Show procedure line separators".
I was just going to mention that option and you did it first. :)
Does that do what you want?
Unfortunately that option is of no use to me as I'm coding in C++. Yet top-level outlining-based implementation would be perfectly fine for me.
BTW, if/when this is being implemented, we should probably come up with a better name than using “procedure” (as it's irrelevant to C++) or “method” (as “bare” functions are not methods). I'll be glad to collaborate.
“Productivity Power Tools 2015” had the “Structure Visualizer” sub-extension which could show, among others, separator between methods. While Visual Studio 2017 incorporated one (main?) feature of the sub-extension (structure guide lines) the “Productivity Power Tools 2017/2019” no longer includes the said sub-extension, so the “separator between methods” got lost. Given that “Editor Guidelines” implements a visually related feature also previously part of “Productivity Power Tools”, this is IMHO quite a natural extension to add the missing “separator between methods” feature to.