Re: Main Thread UI and Detached Thread
Re: Main Thread UI and Detached Thread
- Subject: Re: Main Thread UI and Detached Thread
- From: Ken Victor <email@hidden>
- Date: Mon, 31 Mar 2008 13:23:28 -0700
At 1:08 PM -0700 3/31/08, email@hidden wrote:
Date: Mon, 31 Mar 2008 12:20:41 -0700
From: Mike <email@hidden>
Subject: Re: Main Thread UI and Detached Thread
To: Apple Cocoa List <email@hidden>
Message-ID: <email@hidden>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
I have two methods in the main thread that I call from the worker using
performSelector, etc. The method for updating the progress bar for
example looks like this:
- (void)setProgressBarValue:(double)value
{
if( progressBar )
{
[ progressBar setDoubleValue:value ];
[ progressBar setNeedsDisplay:YES ];
[ progressBar display ];
}
}
are you calling:
performSelectorOnMainThread:withObject:waitUntilDone:
(or one of its variants) passing in a selector for setProgressBarValue: ?
could it possibly be that setProgressBarValue: takes a double
argument, yet performSelector... expects an id for the withObject
parameter? thus, you have potential garbage being passed to your
setProgressBarValue method.
ken
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden