Re: Nested sheets
Re: Nested sheets
- Subject: Re: Nested sheets
- From: Guy English <email@hidden>
- Date: Thu, 31 Mar 2005 10:35:57 -0500
Hi Bill,
Well you've just about got a book written on the subject with the
mails you've sent recently! My take on it is that, like the Apple
Script interface, you could always have an accessory view with a
checkbox to control the overwrite behaviour. I think it should
*always* be there in an import dialog - so that use user is aware that
there can be an issue if nothing else. On the other hand it's a little
scary having a flag in the UI asking if it's ok to destroy some of the
users data ... so ...
It's not clear what these files contains exactly. But if each file
contains a number of records and, during an import, some of these
records will be added and others might be overwritten then I think you
need to let the user know exactly what's going on. Upon detecting a
potential overwrite open a new window with a list of all the records
that will be effected by the import operation. Model it like the iSync
conflict window for extra points. Have the user choose on a record by
record basis what to do and provide a couple of buttons for "keep all
originals" or "take all new records". It's more work than what you're
talking about but it's slick, expandable, understandable, and there is
precedent for it in other apps. I believe Pages will pop up a dialog
with fonts that are missing if you import a Word file for example. I
think your hesitation comes from the idea of popping up a lame Windows
style "Yes" "No" "Cancel" dialog - you don't have to do that. You can
take the opportunity to give the user a great feeling of control over
exactly what your app is doing.
Take care,
Guy
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden