Graeme Geldenhuys wrote: >>> code folding. The idea of "draw code divider" was simply to draw a >>> horizontal line at the end of each procedure or method (like visual >>> basic 6 did). I have no interest in drawing horizontal divider lines >>> wherever code folding can occur. And with the current verbose level of >>> >> That can be looked at / I can see the benefit of such a feature. >> > > Before horizontal line drawing between procedures / functions, I have > seen programmers add spaces to separate methods. Or use comments as > dividers. eg: {-------------------------------} > > Those are all waisted efforts and get in the way of coding and > programs such as 'pasdoc'. The visual effect of synedit drawing the > line (without anything actually being in the source code) is brilliant > and gives a much better look! > > I think it will be worth having as a separate feature to code folding. > And at the moment I can only see it being useful between procedures, > functions and methods. I would ignore nested methods for now - it can > be added at a later date if the need arises. > If you set the draw level to 3 or maybe 4, you should get the correct divider draw levels. You will have to ignore the dividers drawn at the end of implementation sections....
>> Not sure where it gets broken? Are the pictures from different versions >> of lazarus? or are they with different settings? >> > > Nope, the screenshots in the bug report is all taken using the same > project, settings and Lazarus version. I simply switched tabs and took > screenshots. > so they are all with "Settings: Code Folding: Enabled Divider Draw Level: 1 " ? In that case the first picture is wrong => with DDL=1 there should be no line between procedures (it would be at the end of the unit level.) Not sure if complete: DDL 1: unit level DDL 2: implementation/ interface DDL 3: Procedure implementation / class declaration since you only switched tabs => did you aybe change config in your session? maybe the issue was that the config change was not set to all editors? > >> If you want then at begin/end level you need to set the divider draw >> level higher => the down side is, there will be additional dividers. >> This may not be the effect you desire, but it is the effect intended. >> > > I think my original idea or method dividers got lost somewhere. :-) I > only indented the feature to have dividers between procedures, > functions and methods. No nested methods and no other code folding > areas. > try level 3. Best Regards Martin _______________________________________________ Lazarus mailing list Lazarus@lazarus.freepascal.org http://www.lazarus.freepascal.org/mailman/listinfo/lazarus