I'm guessing clicking table items causes a different PDF to be
displayed. If so I suspect when you click through them quickly what's
happening is a previous call to your thread is completing when a new
PDF is supposed to be displayed and you'll need a way to cancel the
loading of the previous request when a new one is needed. This could
be done by giving each request a unique ID and having the PDF view
discard (or cache off screen for later) replies for abandoned requests.
On May 6, 2008, at 5:19 AM, Karl von Moller wrote:
Yes I tried that only moments ago. I actually went to the trouble of
completely rebuilding the Application again by not using Threads.
Instead I'm calling everything from the main thread as it were -
directly. The application is pretty solid and function without
crashes. I also got rid of the progress indicator as I'm now dubious
on those also. In the Non thread version, the Progress Indicators
slowed the app down considerably.
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
