🚀 go-pugleaf

"nicolasr" <nicolasrATSIGNgmx.net> wrote in message
news:3e7f8a59$1@newsgroups.borland.com...

> I'm trying to automate another application by sending
> messages to its main form and child controls like buttons etc.
> The problem is that many Windows messages have pointers
> to structures as WParam/LParam. As far as I know those
> pointers are invalid in the address space of the other
> application, is this correct?

Correct.  Only WM_COPYDATA allows data to be migrated between processes
without having to worry about the difference in address spaces.

> I have to select an entry in a list view in report style.
> The messages LVM_FINDITEM and LVM_SETITEMSTATE
> both don't work since they require pointers as parameters.

You have to be in the address space of the destination window in order to
send messages that use pointers.

> Is there any common workaround for those cases?

The only way I know of is to write an separate hook DLL that is designed to
intercept window messages, and then use SetWindowsHookEx() to inject the DLL
into the address space of the destination application.  Then you can send
the destination window a known message that the DLL can filter for and then
handle sending the LVM_... messages to the destination on behalf of your
application.


Gambit