| |||
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
I suppose it's possible. The spawned thread does a lot of setup then iterates some arrays of a bunch of objects in the filesystem that it needs to delete. The idea is to update the progress bar one increment with each item being deleted. I'm using a MacBook 2.16 Ghz but I doubt that the main thread is too slow to be able to do the updates.
Also, I set a message text item with the name of each item being deleted in the window as the worker thread runs. I never see it change even for an instant. I find it hard to believe that there can't be any visual update no matter how quickly the worker thread completes.
Hank
Hank Heijink (Mailinglists) wrote:Just checking the obvious here - is it possible that your worker thread completes its work so fast that the main run loop hasn't updated the screen once before it's done? Keep in mind that the main thread has to display your window with the progress bar and the text and (depending on your implementation) that your worker thread may be working (and completing) while that's being done.
On Mar 30, 2008, at 2:55 PM, Mike wrote:I have all my UI running on my app's main thread. I have a worker thread that I detach with detachNewThreadSelector:toTarget:withObject: (my worker thread).
In my worker thread I do a tight processing loop and one of the things I do in the loop is call two methods in the main thread to update the display (a text message and progress bar) - via performSelectorOnMainThread:withObject:waitUntilDone:modes.
However, when the loop runs in the spawned thread, the display doesn't get updated. If I insert a sleep(1) call into the loop, then the display updates.
Why doesn't the main thread process the changes to the UI unless I call sleep? I thought the whole idea of using a separate thread was so that the main thread could continue to run on its own?
Thanks,
Mike
_______________________________________________
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: http://lists.apple.com/mailman/options/cocoa-dev/email@hidden
This email sent to email@hidden
_______________________________________________
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:
http://lists.apple.com/mailman/options/cocoa-dev/hank.list %40runbox.com
This email sent to email@hidden
_______________________________________________
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: http://lists.apple.com/mailman/options/cocoa-dev/email@hidden
| References: | |
| >Main Thread UI and Detached Thread (From: Mike <email@hidden>) | |
| >Re: Main Thread UI and Detached Thread (From: "Hank Heijink (Mailinglists)" <email@hidden>) | |
| >Re: Main Thread UI and Detached Thread (From: Mike <email@hidden>) |
| Home | Archives | FAQ | Terms/Conditions | Contact | RSS | Lists | About |
Visit the Apple Store online or at retail locations.
1-800-MY-APPLE
Contact Apple | Terms of Use | Privacy Policy
Copyright © 2007 Apple Inc. All rights reserved.