Well, let's consider this as my personal feeling :) It just bothers me, that's all. Since yours, Barbara's and Cetin's opinions are very valuable for me, I will not continue to argue :)

And I really have to play with your class, when I find time for it.

Thanks again.

>Actually, calling Init() in code is not breaking any events sequence, because you just execute the code in it and not causing the Init event to happen.
>
>>Barbara,
>>
>>Thanks for the response. Ok, now I'm in small ("v men'shinstve"). I thought calling Object.Init method from another object method breaks events sequences, but I may be wrong here, since you, Nick and Cetin don't consider it's being something ubnormal...
>>
>>Ok, thanks again.
>>
>>>Nadya (and Nick)
>>>Just IMHO, but I agree with Nick about re-using the INIT() code. I started doing this when I realized that I had several subclassed grids and they all repeatedly called code that was called from the INIT(). For several I used a single subclass with a "ShellFromInit" (or in Visual Maxframe their ShellAdditionalInit() ) method but others needed more complex coding and each grid seemed to be different. I was ending up with multiply nested methods.
>>>
>>>Finally I opted for just putting the code that was always needed for resetting properties into the INIT() and only putting code called under special circumstances into a separate grid method - it was simpler, easier to track and always the same no matter whether I was using a grid from VMF, a VFP base class grid or Nick's Grid Highlighter.
>>>
>>>Just my $.02 US
>>>Barbara
>>>