[Lazarus] update [Re: Code Folding mess and Code Divider feature]

[Alexander Klenin]

On Fri, Apr 10, 2009 at 22:10, Martin Friebe <lazarus at mfriebe.de> wrote:

>> 3) 'Folding'/'Divider' buttons are slightly confusing. Maybe it is
>> better to make common list
>> of language constructs with additional 'Fold' checkbox, and make it
>> visible only when needed?
>> Alternatively, how about at least using PageControl instead of two buttons?
>>
> I don't like the page control to much, I tried it....
> The more likely solution (and feedback shows it will be needed) is to
> have 2 complete independent pages in the tree on the left.
>
> Patches are welcome, I have some other stuff that I currently prioritise
> at a higher level

Sorry, no patch from me, but I can create an issue if you want.
I have no problems with a separate page,
but why do you reject a common list? It seems the best solution to me.

>> 4) Some combinations result in two dividers drawn separated by and empty line
>> (e.g. after the last procedure and before the initialization section).
>> IMHO in such cases
>> only one divider should be drawn
[skip]
> Simple drop them would not work for people who have them in different
> colors (ok ,I do not honestly believe this is an issue)

BTW, don't you think that per-type divider coloring is an overkill?
Perhaps a single color on Colors page would be sufficient?

> An other way, would be not to determine if we already drawn some other
> divider, but instead to end those blocks always in front of any empty
> lines (as long as those empty lines are at the end of this block). It
> would however mean that (if differently colored)  the end of a
> type-block is drawn over the end of a class-block, hiding the end of the
> class
>
> I am not yet sure, If, when or which way I will do that.

These are minor things, nothing to worry about too much.

-- 
Alexander S. Klenin