On 4/3/07, Mattias Gaertner <[EMAIL PROTECTED]> wrote:
Can someone give a short example or point me to the right mail, where
AllocateHWnd is needed and why it must be implemented in all LCL
interfaces instead of the LCL?
At some point I thougth about implementing it purely on LCL, but I
discarted this option a little later. It was a implementation option.
I don´t remember exactly the reasons, but I can try to thing again
about it.
Immediately it comes to my mind that Gtk has no window message loop.
So any normal window created on it won´t have a message loop, and
there for you will need widgetset specific code to write this on gtk.
On Qt too. Even if you create a TWinControl, you won´t have access to
the message loop directly, extra code will need to be added.
Further, I don´t know even on windows if just creating a TWinControl
would do it.
For me the really important fact is: Graphics32, Orpheus and other
important packages run better with AllocateHWnd, and that´s enougth
for me.
--
Felipe Monteiro de Carvalho
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
