Paul Ishenin schrieb:
20.10.2011 0:27, Hans-Peter Diettrich wrote:
Since no message IDs exist for other platforms, I'd assume that the LM
messages are equivalent to the WM IDs. But why new names for old names?
Can you give some examples of new names? Or you just complain about LM_
and WM_ pre
20.10.2011 0:27, Hans-Peter Diettrich wrote:
Since no message IDs exist for other platforms, I'd assume that the LM
messages are equivalent to the WM IDs. But why new names for old names?
Can you give some examples of new names? Or you just complain about LM_
and WM_ prefixes?
Prefixes are d
Vincent Snijders schrieb:
What I was against, is letting all windows messages bubble up from the
win32 widgetset interface into the LCL. I am more a proponent of only
passing those messages to the LCL what are handled by the LCL, not all
and very messages that the win32 widget generate.
IMO suc
2011/10/19 Hans-Peter Diettrich :
> Vincent Snijders schrieb:
>
>> What I was against, is letting all windows messages bubble up from the
>> win32 widgetset interface into the LCL. I am more a proponent of only
>> passing those messages to the LCL what are handled by the LCL, not all
>> and very me
Felipe Monteiro de Carvalho schrieb:
I also don't understand the parallel or different WM..., LM..., CM... and
CN... message IDs. Is that separation related to messages handled (or not
handled) by widgets or by the LCL? Or have the LM... message IDs been added
only to prevent cyclic unit referen
Vincent Snijders schrieb:
What I was against, is letting all windows messages bubble up from the
win32 widgetset interface into the LCL. I am more a proponent of only
passing those messages to the LCL what are handled by the LCL, not all
and very messages that the win32 widget generate.
IMO su
2011/10/19 Felipe Monteiro de Carvalho :
> On Wed, Oct 19, 2011 at 2:52 PM, Hans-Peter Diettrich
> wrote:
>> WndProc can preprocess *any* kind of messages, which must be handled in a
>> non-standard way in a specific control, e.g. the TripleClick messages.
>> WndProc finally calls Dispatch, to inv
On Wed, Oct 19, 2011 at 2:52 PM, Hans-Peter Diettrich
wrote:
> WndProc can preprocess *any* kind of messages, which must be handled in a
> non-standard way in a specific control, e.g. the TripleClick messages.
> WndProc finally calls Dispatch, to invoke the implemented message handler of
> the con
Felipe Monteiro de Carvalho schrieb:
On Wed, Oct 19, 2011 at 1:56 PM, Hans-Peter Diettrich
wrote:
Can somebody explain the purpose of e.g. WindowProc, WndProc and
MainWndProc, in the LCL?
Delphi compatibility. AFAIK WndProc works for messages >= WM_USER
WndProc can preprocess *any* kind of
On Wed, Oct 19, 2011 at 1:56 PM, Hans-Peter Diettrich
wrote:
> Can somebody explain the purpose of e.g. WindowProc, WndProc and
> MainWndProc, in the LCL?
Delphi compatibility. AFAIK WndProc works for messages >= WM_USER
> In Delphi MainWndProc calls the handler assigned to WindowProc, enclosed
Can somebody explain the purpose of e.g. WindowProc, WndProc and
MainWndProc, in the LCL?
What's the purpose of TWinControl.MainWndProc, when it's never called or
used otherwise, does nothing, and is not virtual?
In Delphi MainWndProc calls the handler assigned to WindowProc, enclosed
in try
11 matches
Mail list logo
