Re: ? re: Win32lib and onClick
David, Brian,
Thanks for your work on this. I'm learning a lot from the discussion.
David, it's interesting what you said about processing the WM_MESSAGES.
Before I posted my question, I looked through some old reference books on
Turbo C++ and the old Borland OWL (which I never really understood) to find
a way to intercept messages. From that, and looking at some example
programs, I cobbled together an event intercepter without really
understanding what I was doing. Not unusual for me, I'm not really a
programmer, I'm used to programming by voodoo.
So I started it up. Surprise! It crashed. Fortunately, it didn't bring down
the entire system, just the program. Nothing seemed corrupted/damaged, no
infinite loops that I could tell, but it sure as shootin' didn't work.
Yesterday I tried the onTimer. It took a little while for me to learn how to
use it, but once I got it working, it worked like a charm, and I can't
really tell I'm not in a tight loop. I'm curious to see exactly how much
slower Brian's code is, and what it does. I might try it at home this
weekend, where my chances of unleashing global devastation are somewhat less
should I goof something up between the reading and the implementation.
Sherm
|
Not Categorized, Please Help
|
|
