Re:OWL custom controls
I worked with the editors of the late Borland C++ Journal from The Cobb
Group for the Nov 1995 issue on how to use OWL to write Custom Controls.
Back then the controls even worked inside the Borland Resource Workshop and
were compatible with 16-bit and 32-bit OWL.
What we did back then was create our own TCustomControl inheriting TWindow
and then overriding specific functions.
You also have to create your libmain or dllentrypoint for 16-bit or 32-bit
and inside there you create your module and register your class that you are
referring to in your posting. This is not like an ActiveX control though.
There is nothing to do with the registry etc, just a RegisterClass function
in the DllEntryPoint.
I hope this helps.
-Tom
"Mohsen" <
XXXX@XXXXX.COM >wrote in message
Quote
"Mohsen" < XXXX@XXXXX.COM >wrote:
>
>Hello to All and Happy New Year,
>
>OWL custom controls such as TGauge can be inserted into dialog
>resources using specific class names assigned to them (such as
>OWL_Gauge for TGauge). When the dialog resources is loaded (by
>Windows not OWL right?) the system knows about class names
>(OWL_Gauge in this case right?). So such OWL custom controls
>should be registered with Windows prior to loading the resource
>in some sort of ways (RegisterClass or something). The question
>is how the control is registered when the control object does
>not exist yet (the constructor has not been called). Any idea
>would be appreciated.
>
>Mohsen
OWL registers custom controls before the resource of the dialog
is loaded. This registeration is done using TWindow::Register.
However special care must be taken to correclty hand TModule
pointer specially when dealing with DLLs, in other words when
the dialog resides in EXE file and the control in DLL or vice
versa.
Mohsen
{smallsort}