Data transfer between other programs and Girder?

[Mark F]

Using a global shared memory area and a couple of semaphores in a new plugin would be my choice; however, I'm biased. I've already written a plugin to do this for hardware events. :) It could be expanded to include setting variables pretty easily. I wrote it to support the ATI RemoteWonder but didn't finish testing before two other solutions appeared. :oops: Would you like the MS VC++ 6.0 source? I don't have it here but could send it this weekend. PM me with your E-Mail address if you want a copy.

Another idea: Can the system() function be pointed at a Windows shortcut? If so, you could make a shortcut to the IP Client that started it minimized and execute that shortcut from within your program.

[vynce]

I'm looking for ways to send data from a C++ program that I'm writting to Girder.

The contents of Girder variables can already be transferred to other programs through the command line, but transferring data back to Girder is much more difficult at the moment.

I currently have my program write the data to a file and then read it back into Girder using Lua. This is rather slow and seems a bit messy for transferring a single string.

The internet event client could be used and the data could be sent as a payload. I guess I would use the system() function for this (?). But this has the down-side of popping up a console window. Is there some way to prevent the console window from popping up? If I could get the handle for the ieventc console window I could use ShowWindow(hwnd, sw_hide).

Another option would be to build an internet event client directly into my program. After reading ieventc_readme.txt this looks pretty difficult. Any code snippets or related things I could look at?

I think that the best option would be to have some kind of data transfer plugin that other programs could interface with.

Thanks for any help/ideas.

[vynce]

Thanks for the ideas guys. I might do some more looking around with those ideas in mind. I just realized that DVDSpy does everything my program does (and much more). So I'll probably stop developing this program for now - I learned a lot though :)

[Snakebite]

I use mailslots instead of shared memory. Usually you want synchronization, signalling of available data and queueing when transferring data between processes - mailslots have it.