Home > Software engineering >  Consult communication problem between VB and their own writing DLL..
Consult communication problem between VB and their own writing DLL..

Time:11-12

Intercept external program text box EN_CHANGE news, code written into DLL

In the callback function CallBackHookProc process messages, text box en_change trigger message, after get the textbox text how to return to the main program?

1, the main program window text box HWND pass into the DLL in the form of parameters, and then every time message triggers WM_SETTEXT trigger in the DLL main program text box change event?

2, in addition to the Timer control I can't think of any other better way,,,



CodePudding user response:

"Window message processing function" is universal, parameter form, the number has "agreed,"
You can search the CallWindowProc function to know about the related content,

You are the "key" across processes message HOOK, this is the system does not support,

To "intercept" need to distance DLL injection...
This involves two aspects of things:
1. Of course, is "remote injected DLL" technology;
2. You want to use VB6 write DLL, if "the other" is not written in VB6 exe,
So you need to use TLB to declare all of the API functions,
And all based on VB6 runtime "function (such as a string function) can't use!!!!!!
Otherwise, even if you successfully into the "remote processes", can also lead to "the other process" crash!
  • Related