Robert wrote:
>Yes. It is an installer for all the Windows components of the windows
Package. The script is in

Great.  I guess if you want to add the conduit to the mix, I can send along
my Inno script once I finish off the conduit (hopefully in a week).

>It is using the tools to provide a separate commandline stub, as well as
the toolchain for
>whatever batchfile/automatic execution are already in use.
...
>The Desktop bypasses it and just calls the python script directly, since
the Windows API is
>[still] deficient in regards to killing a process. The Microsoft API only
allows proper killing

Does this mean the Desktop is actually using none of Dirk's stuff? I.e. if
I have the Desktop installed, can I delete everything (the exe's and dll's
I mentioned earlier) except the desktop exe (and resources) and the
pyplucker stuff?  If this is the case, then perhaps there is no need for
Dirk's stuff anymore (other than to support those using the command line
versions)?

>The Microsoft API only allows proper killing
>of a process by sending a close event to a window, and a windowless
application obviously has
>no windows.

Hmm, I thought there was something in CreateThread that would allow the
thread owner to kill it.  I guess you would have to spawn 2 processes then
instead of 1.

Bill



_______________________________________________
plucker-dev mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-dev

Reply via email to