Re: How best for dll to "report progress"?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance


"J French" <erewhon@xxxxxxxxxx> wrote in message
news:4555fe91.1056328904@xxxxxxxxxxxxxxxxxxx
On Fri, 10 Nov 2006 17:12:34 -0600, "MP" <Nospam@xxxxxxxxxx> wrote:

<snip>

Probably that DLL is working inside AutoCad's process
eg: it uses AutoCad's memory and thread

exactly


4) All this stuff about DLLs is a red herring
A red herring is something that looks like an interesting clue, but is
really irrelevant

hmmm, don't know why it's irrelevant since it's my main question.
How can a dll report back periodic progress events to the app which created
it?

It sounds as if you and Ken are saying a dll can't Raise events
Sure DLLs can raise Events

well, that may be my solution then, i'll try it.

- Ken and I think that you are trying to get two separate EXEs to talk
to each other
- and that can be done too

no, not sure why you're thinking that, I'm just asking how to get one dll to
talk to one exe

Why not give the DLL a Progress Form ?

I've had problems in past trying to show a Form from a dll in acad.
(due to lack of knowlege), problems with modal /non modal / component
request pending / switch to other component dialog / mess and confusion....
so I've shyed away from trying that.

I'm trying to get my exe form to act as the task manager/ progress reporting
form combination.
The idea is I have several command buttons on the form, also several lables
and a progress bar
So you can select from various tasks via command button, that "wakes up the
dll" and as it does it's thing inside acad,
the labels tell you whats' going on, (mostly to entertain the user and
convince them that in fact the app hasn't just frozen up :-)
and the progress bar gives additional visual cue of activity.

Maybe I should revise that tack and move the progress bar into the dll?


Marshalling an event should be instant to a human

seems that's not the case with acad.
Here are the results from doing the exact same thing either using my dll in
process or using the same code but marshalling across acad's process
boundary
The dll simply blows the standard exe out of the water - 50 to 1 !!!

'-**************************************
'time while running in ide in group project
'Processed 1600 blocks in 105 seconds
'Items searched: 21742
'-**************************************
'timing in compiled exe and compiled dll
'Processed 1600 blocks in 2 seconds
'Items searched: 21742

If you have a HWND then you can tell it what to do, even if it does
not belong to your App

Well, in this case I don't have an hwnd(that I want to talk to), just my exe
and my dll.
Unless you are suggesting that I could use a textbox in my exe form and have
the dll send messages to it, the way I now want to send messages to labels
on the form.

Command Line is stuff you send to an EXE when you launch it
Well I haven't created any command line stuff for my app, don't know how to
do that.
I just launch it by double clicking on the file(or create a shortcut to it)

what textbox in autocad?
Any you can create - I don't know AutoCad

again, i don't have or need a textbox in acad.
My form is in my exe.
It has textboxes for other things but I'm trying to just use a lable
(lblCurrentProcess.Caption = ) to report progress
- and a progress bar for visual stimulus :-) - wow, really cutting edge
<vbg>


Thanks again for your patience with these beginner questions.
:-)
Mark


.

Quantcast