Re: NSTask, NSPipe's and interactive UNIX command
Re: NSTask, NSPipe's and interactive UNIX command
- Subject: Re: NSTask, NSPipe's and interactive UNIX command
- From: "Sven-S. Porst" <email@hidden>
- Date: Wed, 2 Jan 2002 22:26:24 +0100
>
The problem is that notifications of available data on the output pipe
>
are fired only *after* "command" has exited! That is, the behaviour of
>
this code is as follows: "command" is run but no output is shown;
This may not be of much help but I currently have a similar problem to
yours and was about to ask a similar question. In my case I call an
application via NSTask that takes a few seconds before giving it's first
output. My setup is pretty much the same as yours. Unfortunately I don't
get notified of this and hence cannot respond to the application's output.
While playing around with this, I discovered that using my own
application (say, by opening several menus, particularly the services
menu or the menu of a popup-button that is in my window, will eventually
trigger the notification - even before the command line application has
exited.
I am very confused by this behaviour - but then I am very new to the
notifications and stuff, I've basically just followed the documentation
and examples (none of which treat the case of 'interaction' with a
command line application incidentally).
Any hints as to what may be going wrong are greatly appreciated.
Happy new year
Sven
--
Sven-S. Porst . PGP: 0x0085ABA3 .
http://homepage.mac.com/ssp
"Science is magic that works."