| Re: Update IDL Widget from C++ [message #47013] |
Wed, 18 January 2006 12:40 |
mtrutledge
Messages: 4
Registered: January 2006
|
Junior Member |
|
|
Shared memory is a great idea. I think I will try that with a widget
timer event.
Thanks guys.
Matt
JD Smith wrote:
> On Tue, 17 Jan 2006 12:01:16 -0800, mtrutledge wrote:
>
> Shared memory is also an option, and probably the best option if you
> need to send large amounts of data over to IDL. Whatever you choose:
> socket, temp file, shared memory, you'll have to poll in IDL to check
> for changes, likely using a widget timer event. Depending on how fast you
> need things to update, this may not be ideal.
>
> JD
|
|
|
|
| Re: Update IDL Widget from C++ [message #47025 is a reply to message #47013] |
Tue, 17 January 2006 16:36  |
JD Smith
Messages: 850
Registered: December 1999
|
Senior Member |
|
|
On Tue, 17 Jan 2006 12:01:16 -0800, mtrutledge wrote:
> I would like to avoid writing a temp text file for IDL to read.
> Communicating to IDL widget through sockets sound interesting, does anyone
> have information on this?
Shared memory is also an option, and probably the best option if you
need to send large amounts of data over to IDL. Whatever you choose:
socket, temp file, shared memory, you'll have to poll in IDL to check
for changes, likely using a widget timer event. Depending on how fast you
need things to update, this may not be ideal.
JD
|
|
|
|
|
|
| Re: Update IDL Widget from C++ [message #47030 is a reply to message #47028] |
Tue, 17 January 2006 11:02 |
henrygroe
Messages: 30
Registered: August 2003
|
Member |
|
|
The simple/dumb way that pops to mind would be to have the C++ code
write to a scratch file on disk every now and then that the widget
would monitor.
I'm sure someone else has a more elegant solution, perhaps involving
"socket"?
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
