In fact, the GTK object has to be created whenever the fComponent is addressed, which is…
Show quoted text 9 lines
In that case people should not refer to .fComponent, but .Handle (whose getter calls HandleNeeded which actually creates the control. I have actually implemented all this in my copy and will be ready for checking in soon by someone).
One solution would be to make Component property and GetComponent it's read method, which would create the component on demand, or have a method like ComponentNeeded.
As you say. Delphi does this in handleneeded.
The Windows way (of creating controls), however, is VERY different, which might be a problem.
They are different but it isn't actually a problem. I once wrapped some C graphing tools (Quinn Curtis - pretty nasty I thought) as Delphi controls and they were like this, but it worked OK.
Show quoted text 5 lines
But in the end it doesn't matter if the visible properties (caption etc) are set via messages or psuedo-properties.
Show quoted text 11 lines
Its not really a drag, its fully "automatic". There is no problem with it at all.
Sam
