| Re: IDL and external app in concurrent mode [message #22902] |
Tue, 12 December 2000 09:23 |
Craig Markwardt
Messages: 1869
Registered: November 1996
|
Senior Member |
|
|
barban74@my-deja.com writes:
> Hi everybody,
> my name is Andrea Barbaresi and I work in the research center
> of Telecom Italia Group, here in Italy.
>
> I read on "External Development Guide" that
> "IDL was not designed to be used in a threaded program" so
> I'd like to know if it's possible to accomplish, both in Windows
> and in Unix environment, a task like the one
> described below:
>
> Use a C++ program to activate a IDL widget-app
> in a non-blocking way (by means of "IDL_RunTimeExec()"
> statement?); after this call the program must be able to continue
> its execution and periodically give back the control to IDL to
> check if there are any messages from the GUI created by widget-app.
Hi Andrea--
I think your best bet is to use two separate programs with a means of
communication between them. Under Unix this is best accomplished with
a pipe. While it would be useful to use SPAWN, I'm not sure IDL is up
to the task since you probably want two-way communication. Also, you
probably want non-blocking I/O. Under Windows I'm sure there is some
similar IPC mechanism, but it's been a while. It used to be DDE but
that's been superseded I think.
Good luck,
Craig
--
------------------------------------------------------------ --------------
Craig B. Markwardt, Ph.D. EMAIL: craigmnet@cow.physics.wisc.edu
Astrophysics, IDL, Finance, Derivatives | Remove "net" for better response
------------------------------------------------------------ --------------
|
|
|
|
| Re: IDL and external app in concurrent mode [message #22905 is a reply to message #22902] |
Tue, 12 December 2000 08:09  |
Nick Bower
Messages: 43
Registered: June 1999
|
Member |
|
|
I wish there was more discussion about ION from people involved with it,
because I don't know *anything* about the package, but what about using
Java and calling ION libraries from that?
Surely you'd have heaps more control over threading and interfaces when
using libraries instead of spawning separate IDL applications.
Beware though - I don't know anything about this and am just trying to
spark some conversation about it. :-)
barban74@my-deja.com wrote:
> Hi everybody,
> my name is Andrea Barbaresi and I work in the research center
> of Telecom Italia Group, here in Italy.
>
> I read on "External Development Guide" that
> "IDL was not designed to be used in a threaded program" so
> I'd like to know if it's possible to accomplish, both in Windows
> and in Unix environment, a task like the one
> described below:
>
> Use a C++ program to activate a IDL widget-app
> in a non-blocking way (by means of "IDL_RunTimeExec()"
> statement?); after this call the program must be able to continue
> its execution and periodically give back the control to IDL to
> check if there are any messages from the GUI created by widget-app.
>
> Can it work ?
> (Does the XMANAGER statement in IDL program return immediately or not ?)
>
> Are there alternative ways to do the same task?
>
> Should I think about a different scenario where there are two concurrent
> processes,
> with IDL program that pass widgets events to the C++ program
> in one way or another?
>
> Can "non block" widgets be usefull ?
>
> It is possible to have a shared memory between the two processes?
>
> Any help or suggestions will be very much appreciated,
> thanks a lot!
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
