>Hi Dragan ...
>
>>Therefore, a rule of thumb: give your subclasses meaningful names, different from parent names.
>
>I can't use different name for the subclasses ... because i use this equivalence in the engine of Verticalization of programs.
>
>There is no problem and all work very fine, but when in design mode i use two sublasses there is this problem ... the only way to avoid the merging is to work with one subclass ... so issue a CLEAR ALL and work with the other subclass.
>
>Anyway i consider this behavior an error.

Still, there is no way to suppress it, even if naming the class the same as the parent was forbidden: you can have two sibling classes with the same name, same parent, in two classlibs, even if they were named differently from the parent. Anyway, placing any restrictions here would defeat the scheme where you can subclass the classes developed elsewhere (bought, downloaded, inherited from your rich grandfather...).

>PS: Sorry for my bad English.

Not bad at all... but then I'm not the one to judge, anche io sono strano qui (corretto?).