That's an interesting thought. But if it was done as a compiler/linker flag,
I assume you'd have to specify that the entire data segment was shared. I'm
not certain what the ramifications of that might be.
Yeah, what I seem to be finding is that the hook "breaks" as soon as Windows
tries to map the DLL into another process. For example, I installed a
keyboard hook (not low-level) and it works when the app is active. It also
works if I activate another app and then go back to the original app. But if
I activate another app and type some keys, then the hook stops getting
called, even if I reactivate the original app.
I'm thinking it may have something to do with either initializing the VB
runtimes, or that the VB runtimes just don't like being mapped this way.
Yeah, kind of. Some folks have made some assertions about VB and I'd like to
prove them. Unfortunately, there may be issues unrelated to those in
contention that prevent me from doing so.
Available for consulting: http://www.yqcomputer.com/