Re: How best for dll to "report progress"?
- From: erewhon@xxxxxxxxxx (J French)
- Date: Fri, 10 Nov 2006 10:10:06 GMT
On Fri, 10 Nov 2006 00:36:40 -0600, "MP" <nospam@xxxxxxxxxx> wrote:
<snip>
The dll is created by my vb6.exe app "in process" to the external app(acad).
The dll can then "communicate" to the external app(in whose process it is
running) by calling that apps api methods etc.
Then it can return data back to my vb6 exe when I call it's properties,
right?
Sub()
Set oApp = CreateInstanceOfApp
Set cDll = oApp.GetInterfaceObject(mydll.myclass)
Call cDll.GatherInfo (oApp.Document)'dll communicates with app ???
ReturnData = cDll.ReturnInfo'dll communicates with me???
Call UseData (ReturnData) 'or whatever
End Sub
<snip>
This sounds as if:
1) You have AutoCad running and it has some sort of VB inside it
2) You have another pure VB EXE
3) You want to make the things talk to each other
4) All this stuff about DLLs is a red herring
Basically it sounds as if you either need to set up some form
communication such as WM_COPYDATA or 'Chat by Textbox' or you need to
turn your pure VB App into an AX EXE
PostMessage is not going to be much use for all but the most trivial
things.
Cross Process Marshalling (which is really SendMessage in drag) is
slow, but 'slow' is a relative thing - unless you have two Apps stuck
in tight loops without processing their Windows Message Queue then
that 'slow' communication will be pretty darn quick in human terms.
Personally I would Shell your pure VB App with the HWND of a Textbox
in the Command Line and use WM_SETTEXT to talk back from the pure VB
App to the Textbox in AutoCad.
It is simple to set up, and will give you a good idea of 'speed'
.
- Follow-Ups:
- References:
- How best for dll to "report progress"?
- From: MP
- Re: How best for dll to "report progress"?
- From: Ken Halter
- Re: How best for dll to "report progress"?
- From: MP
- How best for dll to "report progress"?
- Prev by Date: Re: Loose coupling, tight cohesion, general confusion <g>
- Next by Date: Re: Slow application exit on windows 98
- Previous by thread: Re: How best for dll to "report progress"?
- Next by thread: Re: How best for dll to "report progress"?
- Index(es):
Relevant Pages
|