On 1/26/2011 13:43, Frank Church wrote:
On 26 January 2011 18:29, waldo kitty <[email protected] <mailto:[email protected]>> wrote: On 1/26/2011 13:08, Frank Church wrote: After having sparked a much longer thread than I expected, I need to get back to my problem, although it may belong in a different thread. Now in most case data modules expose interfaces that the GUI parts of the app call to get data. My problem now is the other way round, where the Data Module needs to connect with the GUI first, in that whether or not the GUI is running, the Data Module can make a call and send the data to it if it exists, but without having to compile in any GUI dependencies. in this case, i would consider a pipe (named or otherwise)... create the pipe when the GUI unit starts up ... the data unit looks for the pipe... if it does not exist, it does not attempt to communicate with the GUI part... when the pipe comes into existence, then the data unit can start sending its data into the pipe... seems workable ;) Pipes are a new area for me, are there any Lazarus demos of their usage?
uncle google found this while searching for lazarus fpc "named pipe" http://lazarusroad.blogspot.com/2006/12/only-one-instance.html there are others that show up as well... -- _______________________________________________ Lazarus mailing list [email protected] http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
