A vote for bold, as it is both readable and these constants also introduce a block of code like "if...then", "for...do" or "while...do" which are reserved words -> have the same highlighting as default, so this would be consistent (yet preserving the string/number/identifier highlighting)
As I see, I'm the only one. No problem I think every opinion is important :P "probably lot's off people will never know it is even possible." By the way actually I didn't know till this conversation but now for sure I'll turn it to bold :) Krisztián 2010/5/25 Martin <[email protected]> > On 25/05/2010 19:19, Vladimir Zhirov wrote: > >> About the feature: >> Personally I turned it off, since for me indentation >> makes case-labels readable enough. >> >> But we could consider it to be ON by default not to go >> unnoticed by people who would like it. Those who don't >> like it can disable it forever in few clicks. Since it >> is already in trunk I guess most of us have already >> done so. But if it is disabled by default no one else >> could ever know about it. >> >> > That was my thought. Make people aware off it. > > Sofar I counted 14 replies: > 9 => off > 2 => not specific off, but not liking the current italic > 1 => on, color > 1 => on italic > > (not counting me) > > So I switched it off in trunk again. probably lot's off people will never > know it is even possible. > > > > One more suggestion is to add "case" block to example >> code box of the color settings dialog. This way one >> could instantly see the effect without going back >> to source editor. >> >> > Done => only clicking on the label doesn't (yet) get you to the entry > > > -- > _______________________________________________ > Lazarus mailing list > [email protected] > http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus >
-- _______________________________________________ Lazarus mailing list [email protected] http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
