Hi,
My CoreData app (under 10.4) refuses to save the document once an
exception has been thrown. Its a C++ exception thrown from a menu
command after displaying an alert and it is caught. It happens both
on Intel and PPC, in Debug and in Release mode.
What happens after the exception, is that the save operation fails
without any warning (not even a call to NSLog or [NSException
raise]). If you choose quit after making changes, the save dialog
appears. Choosing save then results in the app menu staying
highlighted, which makes it look as though it is busy, while in
reality it returns to the main event loop. Choosing the save command
manually doesn't seem to do anything. When no exception has been
thrown, saving works normally.
Is this a known bug? Is there a workaround? It's almost impossible
not to throw the exception (its the error routine deep inside a
recursive descent parser)...
Thanks,
Theo
_______________________________________________
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]
