Re: Communicating between Applications
- From: Bob O`Bob <filterbob@xxxxxxxxxxxxxxx>
- Date: Wed, 15 Mar 2006 11:35:18 -0800
Stefan Berglund wrote:
On Tue, 14 Mar 2006 22:25:12 -0000, "Mike Williams"
<Mike@xxxxxxxxxxxxxxxxx> wrote:
in <eSrpmY7RGHA.1728@xxxxxxxxxxxxxxxxxxxx>
"Karl E. Peterson" <karl@xxxxxxxx> wrote in message news:e9m70M7RGHA.1688@xxxxxxxxxxxxxxxxxxxxxxx
There are scores of methods. Probably the simplest would be to passActually that's the way I do it, except that I do it in a way that doesn't require a hook. I pass the "slave" app the hwnd of an otherwise unused (and invisible) textBox in the main "master" app and then the slave app uses the SendMessage API to send the hwnd a WM_SETTEXT message along with a string of your own choosing. The "master" app knows exactly when the message is received because it triggers the invisible Text Box's Change event. An added bonus of this method is that you can send all sorts of different messages back simply by choosing an appropriate string.
an hWnd to AppB on its command line, and then send progress messages
back to that window. Would require a hook --
Mike
Uhh, err um, uhh that would be mailslots.
I've been pondering the appropriateness of mailslots for interprocess comms in
a project of my own. Can you point me to any good tutorial/example/sample/demo
resources?
Bob
--
.
- Follow-Ups:
- Re: Communicating between Applications
- From: Stefan Berglund
- Re: Communicating between Applications
- References:
- Re: Communicating between Applications
- From: Karl E. Peterson
- Re: Communicating between Applications
- From: Mike Williams
- Re: Communicating between Applications
- From: Stefan Berglund
- Re: Communicating between Applications
- Prev by Date: !! DOWNLOAD THE MOST POPULAR 2006's CRACKED SOFTWARE(CAD/CAE/CAM/EDA/PCB/GIS/FEA/CNC)
- Next by Date: test printer code
- Previous by thread: Re: Communicating between Applications
- Next by thread: Re: Communicating between Applications
- Index(es):
Relevant Pages
|
Loading