🚀 go-pugleaf

Hi!
Well, all I can say is that the solution to a problem is always
done with the tools available.

I'm a beginner at C++, and am in the process of teaching myself
how to approach a problem using the concepts of OOP. Part of this
is learning how to tackle a problem in a manner consistent with the
solution techniques available. It isn't always possible, and sometimes
it requires approaching the problem in a different manner.

As a consulting Engineer once told me,
"I want to design an anti-gravity car, and I have it mostly done.
I have the control surfaces for steering, I have the avionics for detecting
other vehicles and obstructions, and I know how to make it descend.
As soon as I solve the small problem of going up, I'll be done."

soo....
Have Fun!
Stephan

"Alisdair Meredith" <alisdair.meredith@uk.renaultf1.com> wrote in message
news:3E672FE1.C4CC3277@uk.renaultf1.com...
Stephan wrote:

> The way around this, for you, is to create a class that inherits the TForm
> and implements your "common" functionality.
> such as:
>     class TCommonForm: public TForm
>
> Then, when you create a new form, change the inherated
> from "TForm" to "TCommonForm"

Not very helpful if you want to add functionality to a group of
controls.  For instance, we wanted to add our own validation/databinding
to several standard VCL controls.  We do not control the base class, and
our implementation must then rely on knowing each possible derived class
in order to cast and handle each correctly.

--
AlisdairM
Team Thai Kingdom