Author Topic: Suggestions for indent guides  (Read 376 times)

Offline RickF

  • Newbie
  • *
  • Posts: 24
  • Karma: +0/-0
    • View Profile
Suggestions for indent guides
« on: June 02, 2011, 05:51:16 pm »
One more very minor feature request.. I love the code folding & indentation marks so I can see where blocks of code start/end.  However, the vertical lines that are visible that are not related to blocks of code I find to be distracting to look at.. The attached image is a code sample showing the issue... It would be great if lines like this (not blocks) would not show the vertical lines for indentations since they're not related to any block but are caused by a line wrapping.

Also, in the same neck of the woods, it would be nice to have a little more spit-polish applied to the indentation marks for blocks with blank lines.. The 2nd attachment below shows this -- I think it would be a more polished look to have the blank lines show the vertical bars to indicate a continuous flow of the block..  Comments?

« Last Edit: June 02, 2011, 08:51:32 pm by RickF »

Offline alex

  • Developer
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1712
  • Karma: +29/-2
    • View Profile
    • HippoEDIT
Re: Suggestions for indent guides
« Reply #1 on: June 06, 2011, 01:14:44 pm »
Hi Rick,

for new request/feature,  please use new post. In such case it will be easier to track requests and other people will find them faster.

Generally, this feature you are talking about called indent guides and have nothing to do with scopes. It just shows "indent" positions corresponding to tab sizes. It happens by chance, that it matches scope positions in your case (because yours code is aligned). It is not a unique feature of HE but something, that is common and exist in some other editors, so going here against "standards" can lead to negative feedback from users, already used with a feature in other editors.. Also for matching of the scopes, you already have nested levels + current scope highlight and in 1.50 paired colored braces.

In addition to all mentioned, calculation of guides positions is very intensive for drawing (they done synchronous) and coding there is rather complicated. So, for this is not a minor change.

About requests themselves:

1) because, as I said feature is indent guides but not scope guides, visualization is OK there, and matches how this done in other editors. While keeping nature of the feature same and trying to recognize situation of formatting indent will be mostly impossible. Can you write formal rule: when to draw guides or not? This will help.
If creating of the new feature like scope indents, this will work, but because there are already several features simplifying scope recognition, it can be too much and maybe not really necessary.

2) here, I think can be done something. At least I see that in N++ this is done like you have requested, so to be standard, can be done...

I will note both requests as ideas for improvement. Feature 2 most likely will be implemented, feature 1 need more detailed discussion/logic model.

In any case both features will go in 1.5x.

BR, Alex.

 

Related Topics

  Subject / Started by Replies Last post
3 Replies
759 Views
Last post July 15, 2009, 02:16:48 pm
by alex
11 Replies
2294 Views
Last post January 19, 2010, 10:38:02 am
by alex
2 Replies
487 Views
Last post April 08, 2010, 08:56:46 pm
by Theno
6 Replies
399 Views
Last post June 08, 2011, 02:17:02 pm
by alex
1 Replies
200 Views
Last post June 11, 2011, 03:13:16 pm
by alex