[lazarus] wndproc

[Curtis White]

I don't remember enough about what all WndProc does, but we should to be careful
here because from what I remember (and have gained from the discussion), I think
the WndProc procedure handles API specific messages that are passed to the
control. If this is the case, then it seems to me that it is going to require a
lot of API calls from the WndProc procedure. So that means it would be calling
right back to gtkint. That seems like extra overhead that may not be necessary
(performance). But like I said, maybe I don't know enough about how WndProc
works. I just want to make sure we don't miss something here.


Curtis

On 16-Aug-99 Shane Miller wrote:
> hmmm..I see that.  I don't see why it would be bad to call
> TControl(Data).wndproc(Message) instead of dispatching them right away.  I
> think that would be a good idea plus it would help with our Delphi
> compatability.  I would also think that this would help in making it easier
> to add other widget tool sets.
> 
> Anyone against this change? 
> Shane
> 
> 
>>>> Marc Weustink <weus at quicknet.nl> 08/16 2:14 PM >>>
> At 12:43 16-08-99 -0500, "Shane Miller" <SMiller1 at stvgb.org> wrote:
>>wndproc is not out of favor for windows controls, but for GTK it is.  
>>Each control sets a callback for EACH signal so we dispatch them that way.  
>>
>>The msg's aren'tr being passed back yet because no one has coded them yet.  
>>A few of them are already coded, like keydown.
>>
>>I'm not sure about converting everything to use wndproc.  How does wndproc
>>handle it then?  Does it simply do a dispatch?  I haven't looked at Delphi's
>>method of handling this, so I'm not awarer of it.
> 
> In delphi the WndProc is merely a big case Message.Msg of.... where finally
> (in TControl) a call is made to Dispatch
> 
> Marc
>