I need a quick sanity check before I post this as a bug... Has anyone else run into a problem with an asynchronous shell where the shell appears to get "stuck" unless if you keep emptying the buffer through the DataAvailable event? Maybe this is how it's suppossed to work and I just never caught on to this nuance. Here is some example code in the open event of a window:
// Setup Shell Shell1.TimeOut = 14400000 Shell1.Mode = 1 Shell1.Execute "dir c:\windows\system32\*.* /s" I'm emptying the shell buffer in the DataAvailable event of the shell via: EditField1.Text = EditField1.Text + Shell1.ReadAll What's also odd is that the EditField receives the first line of the data, but never receives anything else. As mentioned above if I leave the DataAvailable blank, the Shell gets stuck. Hmpph! BTW this is for Windows compiled apps and happens on the Win32 2007r1 IDE as well as OS X 2007r2. Patrick _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
