On May 16, 2007, at 11:43 PM, Bret Pettichord wrote: >> 3. Have the parent process spin, waiting for that file to be created, >> then continue. >> > I wonder whether this is really what is happening. My guess is that it > is blocked... > [...] > I don't think you actually need to have the file polling system. The > reason why is that the click method will not return until the > dialog has > been closed. So you don't need a second synchronization method.
Well duh. Removing the creation of, and checking for, the sentinel file certainly seems to work as you describe. Much cleaner. > Like i said these win32utils seem to provide everything you need and > wrap a lot of the win32api nonesense, so you really would be better > looking at that. I'll check it out. The only advantage over using popen is that you don't have to have an executable ruby file (and know where to find it). You can just require a watcher file and do the work without any implicit or explicit exec. ----- Brian Marick, independent consultant Mostly on agile methods with a testing slant www.exampler.com, www.exampler.com/blog _______________________________________________ Wtr-general mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-general
