Class structure

Cetin, you said in a message to me:

--------------------
...

Or create a derived class and do modification there (harder to implement and follow but fits into OOP better). Something like this:

Create class ;
   HansLocatorGrid of FoxyClasses.vcx ;
AS ;
   LocatorGrid from FoxyClasses.vcx

Or if you want to separate the classlib too:

Create class ;
   HansLocatorGrid of HansFoxyClasses.vcx ;
AS ;
   LocatorGrid from FoxyClasses.vcx

PS: If you apply the last case, be careful some class code have "this.ClassLib" as a reference to its own classlib to create another class from within that library. You may need to copy that class too.
-------------------

If I apply the first alternative (and maybe the second?), and I have this in every "main" file in applications ...

SET CLASSLIB TO "D:\...\Foxy Classes.vcx
SET CLASSLIB TO "D:\...\HansFoxyClasses.vcx

... can I then have only the classes I want in HansFoxyClasses.vcx, for instance, in HansDateTimeCtrls.VCX, only handdtcontrol and hansperiodpicker (and it will still work)?

That is, I leave out datepick. datetimepick, dttextbox, edtexpand, olecalendar, periodselector and timepick from HansFoxyClasses.vcx, but since these are in Foxy Classes.vcx, it will still work?

The advantage with this would be that only handdtcontrol and hansperiodpicker would show up in "View Classes" in the Form Controls Bar.

Regards,

Hans L