Re: The memory could not be "read". Application Crash??
From: Pásztor, Zoltán (pasNOSzPAMtAPor_at_multiXXXlogic.com)
Date: 10/07/04
- Next message: Pásztor, Zoltán: "Re: The memory could not be "read". Application Crash??"
- Previous message: Ian: "Re: The memory could not be "read". Application Crash??"
- In reply to: YYZ: "Re: The memory could not be "read". Application Crash??"
- Next in thread: Pásztor, Zoltán: "Re: The memory could not be "read". Application Crash??"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 7 Oct 2004 12:44:23 +0200
YYZ wrote:
> "Ken Halter" <Ken_Halter@Use_Sparingly_Hotmail.com> wrote in message
> news:#1B97S7qEHA.2816@TK2MSFTNGP10.phx.gbl...
[snip]
>>
>> I've never tried the SoftCircuits control. The feature I wanted most
>> is to be able to set up multiple hooks on the same window (like
>> several instances of a usercontrol trapping messages on their single
>> parent form). The SSubTmr component's the only one I found that
>> specifically supported this feature "out of the box".
>
> I honestly don't know about that feature. I've always gone the other
> way -- added a bunch of subclass controls to subclass all different
> windows. I can't think of a reason that you couldn't subclass the
> same window multiple times...but I just don't know. I lied - just
> tested it. I had 3 instances of the subclass control all subclass
> the hwnd of a form, looking for WM_GETMINMAXINFO. 3 WndProc events,
> all printing debug output of the message and the control name...only
> the last instance of the subclass control got fired.
The reason (from inspecting the source code of the SoftCircuit control) is
that it identifies its clients by the hWnd of the window being subclassed,
and takes great care of ensuring its uniqueness - the first step in
preparing a new hook by any instance (when assigning a new value to the hWnd
property of the instance) is freeing all previous hooks for that window in
the central data structure shared by all instances.
This perhaps could be modified, but the simplicity of the design would
suffer...
-- PZ
- Next message: Pásztor, Zoltán: "Re: The memory could not be "read". Application Crash??"
- Previous message: Ian: "Re: The memory could not be "read". Application Crash??"
- In reply to: YYZ: "Re: The memory could not be "read". Application Crash??"
- Next in thread: Pásztor, Zoltán: "Re: The memory could not be "read". Application Crash??"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|