niklaskallander / vs-unobtrusive-code

An extension for Visual Studio that lets you hide away obtrusive code like comments and logging, to let you focus on the actual flow of your application.
MIT License
24 stars 1 forks source link

Obtrusive code outlining regions #6

Open scottdorman opened 4 years ago

scottdorman commented 4 years ago

Comments

It would be nice if the collapsed comment region behaved like the default collapsed comment region and displayed the first line of the comment as the collapsed region display. Also, when the comment is collapsed, it takes two clicks to expand it. The first click expands it from your collapsed region display (an empty string) to the default collapsed display (the first line) and the second click expands the default collapsed display to the full (expanded) comment. (TL;DR: Your collapsed region contains the default collapsed region for the comment, requiring two expansions to get to the comment text.)

Logging

Having the ability to specify a separate collapsed display for the collapsed logging region would be nice. Not having any display makes the region hard to notice. Also, it should not collapse single lines. (This is more consistent with the default automatic outlining behavior. For example, a "single line" if statement (one without braces around the body of the then-clause or else-clause) doesn't get automatic outlining. It's not until the then-clause or else-clause are wrapped in braces does the if get an automatic collapsing region.)

niklaskallander commented 2 years ago

In regards to the issue with having to click twice to expand the outlining regions, I'm not able to reproduce that at all. Do you have some other extension also added outlining regions to comments?

In regards to not outlining single line comments, I want them all gone myself, but I reckon it could be an option. I'll look into that.

Thanks!

msparica commented 2 years ago

wrt the double clicking, as mentioned in #14 it has to do with the wrapping of the comment in another collapsible block, as far as i can tell

it seems as though the automatic collapsing upon opening the file does not produce this behavior (the automatically hidden comments, presumably managed by the "Collapsed by default" option), i.e. it collapses only the outer block, but if you collapse it manually (or through Edit > Outlining > Collapse to definitions), it collapses the inner comment blocks too, not just the outer ones, meaning you have to expand them as well after expanding the outer block.