Thanks Mike,

I just looked with Instruments and well yes to process the data my app uses 
NSScanner a lot to extract date/time with its corresponding data values, 
so this takes about 99,6% Running-Time (gasp! )…

One error (I think) was that I processed the data inside the 
readFromURL:ofType:error: after it was read into the NSString….but:

Now I pass the NSString fileContent from NSDocument makeWindowControllers to a 
new object WindowController:
It doesn't change anything however, the corresponding WindowController which 
processes now the data is also taking a lot of CPU-time…

Should I put the data processing  in a dispatch_sync queue in the 
WindowController or in NSDocument's makeWindowController ?

Gilles




On 28 Jan 2013, at 14:21, Mike Abdullah wrote:

> 
> On 28 Jan 2013, at 13:18, Gilles Celli <gilles.ce...@ecgs.lu> wrote:
> 
>> Hi,
>> 
>> I've the following problem on OS X 10.6 and later:
>> 
>> My document based app (reads some small and big (150MB or more) ASCII files 
>> to process data, I'm using the method:
>> readFromURL:ofType:error: and returning canConcurrentlyReadDocumentsOfType: 
>> to YES.
>> 
>> When trying to open a bigger file the "Open File Panel" (window) gets 
>> unresponsive (stays open)  for several seconds.
>> For the smaller files the Open File Panel just disappears after clicking the 
>> "Open" button, as expected.
>> 
>> Are there any solution to hide immediately the "Open File" panel after 
>> clicking the "Open" button in an document based app ?
>> 
>> Any help is greatly appreciated.
> 
> Fire up Instruments and find out what's actually happening while the app is 
> unresponsive. Measure or you're just shooting in the dark.
> 


_______________________________________________

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to