Hello Francois, It's the main form class. For functional classes, I always try to keep them small and manageable. However, in the form class, the GUI control declaration, event and message handlers, and GUI related code will make the class large already. Maybe everyone has his/her own standard of large. To me, if I need to scroll up and down a dozen pages to find a function, it's too large already.
-- Best regards, Jack > Currently a class has to be in a single file, at least from the compiler > view. There are tricks: you can use include file, class helpers or simple > class inheritance. > But I think the right solution for your too large class is simple: you > should break it down to a number of smaller classes specialized to handle > part of the problem you have. In other words, you should delegate part of > the work to be done to other classes, each one being in his own file. The > best way to do that is to create components. Either visial components or > non-visual component. > Not knowing why your class is so huge make difficult to give detailed > advice. _______________________________________________ Delphi mailing list -> [email protected] http://www.elists.org/mailman/listinfo/delphi
