>Hi Dmitry,
>
>> So obviously, there is much more that needs to be done when instantiating a form class, even without any code in any methods.
>
>Yes, creating a form involves creating a Windows API window which involves checking user permissions, creating a kernel object, and allocating GDI resources. Forms need to be added to the _Screen.Forms collection, involve a dual instantiation process with the Load/Init event pair, and might cause data environments to be loaded, as well. Scrollable forms require more resources, as do forms with a private datasession. I think the Form would be the worst choice if you need a non-form class.
Thank you for confirming that form is a bad choice. I didn't know about all the things you mentioned above (like GDI resource, collection, etc, etc.). I will stay with custom class then.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
