On Jul 26, 2011, at 11:22 PM, Scott Ribe wrote:
> On Jul 26, 2011, at 5:52 PM, Shane Stanley wrote:
>
>> In Snow Leopard that worked fine; a notification would be sent when new data
>> was written to the file. In Lion, as soon as it's called it goes into a
>> loop; each time readInBackgroundAndNo
On Jul 26, 2011, at 5:52 PM, Shane Stanley wrote:
>> Maybe you should try to re-open your bug ;-)
>
> I did, but no reply.
Too bad, since it seems to me the person who responded didn't know what they
were talking about.
> In Snow Leopard that worked fine; a notification would be sent when new
On 27/7/11 3:18 AM, "Scott Ribe" wrote:
> Maybe you should try to re-open your bug ;-)
I did, but no reply.
Here's some code that's reading a file that's being written periodically:
-(void)dataFromFile:(NSNotification *)notif {
NSData *data = [[notif userInfo]
objectForKey:NSFileHandleNoti
On Jul 26, 2011, at 12:18 AM, Shane Stanley wrote:
>> On Jul 25, 2011, at 3:40 AM, Shane Stanley wrote:
>>
I wonder if they've changed how the readInBackgroundAndNotify works.
>>>
>>> Yes, they have. I logged a bug on it, and was told that the way it worked in
>>> 10.6 was wrong -- whereas
On 26/7/11 1:14 AM, "Scott Ribe" wrote:
> On Jul 25, 2011, at 3:40 AM, Shane Stanley wrote:
>
>>> I wonder if they've changed how the readInBackgroundAndNotify works.
>>
>> Yes, they have. I logged a bug on it, and was told that the way it worked in
>> 10.6 was wrong -- whereas it used not to s
On Jul 25, 2011, at 3:40 AM, Shane Stanley wrote:
>> I wonder if they've changed how the readInBackgroundAndNotify works.
>
> Yes, they have. I logged a bug on it, and was told that the way it worked in
> 10.6 was wrong -- whereas it used not to send a notification until there was
> something to
On Jul 24, 2011, at 11:01 PM, Stephen J. Butler wrote:
> That is, abandon processPipeClose and let each pipe handle its own
> close in the notification when you're sure all of its read
> notifications have actually been delivered. As you've presented it,
> processPipeClose isn't needed.
Your theo
On 25/7/11 3:01 PM, "Stephen J. Butler" wrote:
> I wonder if they've changed how the readInBackgroundAndNotify works.
Yes, they have. I logged a bug on it, and was told that the way it worked in
10.6 was wrong -- whereas it used not to send a notification until there was
something to read, it no
On Sun, Jul 24, 2011 at 10:17 PM, Scott Ribe
wrote:
> I'm using NSTask to run a background process, monitor its output, and
> ultimately present a message to the user. All has been fine with this 10.2
> through 10.6, as far as I know. Now under 10.7 I saw a case where my code did
> not receive
I'm using NSTask to run a background process, monitor its output, and
ultimately present a message to the user. All has been fine with this 10.2
through 10.6, as far as I know. Now under 10.7 I saw a case where my code did
not receive quite all the stdout output from the background process. I sa
10 matches
Mail list logo
