On approximately 12/5/2003 10:19 AM, came the following characters from
the keyboard of Steve Pick:
Hi,
Is there any reason HEM cannot be used in conjunction with the old event
model?
Not that I can think of. I just forgot to add it to that bit.
I'd find it more likely useful to me in the
Hi,
> Is there any reason HEM cannot be used in conjunction with the old event
> model?
Not that I can think of. I just forgot to add it to that bit. My hooks arent
real Win32 hooks at all, as you know, and I put the processing of them after
the NEM stuff so as to make it more difficult to screw
On approximately 12/5/2003 7:00 AM, came the following characters from
the keyboard of Aldo Calpini:
Stephen Pick wrote:
Does typing "$win->Hook(132,\&hello)" class as an "*explicit* request"?
:)
Steve, you have good points. I agree wholeheartedly with you, so what
more can I say? go for it
Stephen Pick wrote:
> Does typing "$win->Hook(132,\&hello)" class as an "*explicit* request"?
> :)
Steve, you have good points. I agree wholeheartedly with you, so what
more can I say? go for it :-)
just a quick note: the NEM, in its present state, is not really
useable. I have different plans fo
Hi Aldo,
>1) you can't easily (I mean, without a lot of effort) intercept all
> kind of messages.
I'm aware of this. Currently this is not meant as a simplicity feature;
the NEM does that already. It's meant as something for people who know
what they're doing when the NEM won't do, so they can
Steve Pick wrote:
> Hello,
>
> Here's a nice idea:
mmm. that's nice, but not as nice as it may seem. I see many problems
with this one:
1) you can't easily (I mean, without a lot of effort) intercept all
kind of messages. this is due to the rather complex nature of
the Windows messaging sys
6 matches
Mail list logo
