On 6/11/12 1:48 AM, Graham Cox wrote:
I believe the 'role' settings are only used by Core Data (if I'm wrong, I'm sure
someone will correct me).
I've run into the same issue. I've had to override -setFileURL: and at that
point "upgrade" the URL to have the appropriate extension so that the modern
version of the file is later written out with the right extension. It doesn't
overwrite the old one because the extension change is seen as a new filename.
When you -saveDocumentAs:, the role seems to be used to determine whether or not
to present an accessory view with a file-type selector. With multiple editor
roles you get the accessory, with only one you don't. So clearly it's being used
by the framework.
I worked around it by checking in -saveDocument: if the file type the document
currently has is one we can actually save. If not, I call -saveDocumentAs: on
super, which suggests the original file path with the new location. In my app
the user gets a warning about the format change when opening an old document, so
all this doesn't come as a surprise.
I tried using -setFileURL: with a changed file extension but that has the
disadvantage of potentially overwriting a file that's already using that name
without any warning (however slim the chances of such a file existing are).
Regards
Markus
--
__________________________________________
Markus Spoettl
_______________________________________________
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
