On Apr 16, 2010, at 18:19, Chris Goedde wrote: > Hi all, > > A few quick interface nitpicks/questions. (Don't you love developing for Mac > users?) > > (1) I'm entering a bunch of books, and I added a field "ISBN". Actually, I > didn't, because BibDesk wouldn't let me. The field is actually "Isbn". I know > this is trivial, but it bugs me. Is there a reason for this restriction?
Because in bibtex field names are case insensitive. There is no way to store any information about what preference you have. Wee need to make a consistent choice, also to (efficiently) compare field names. Capitalizing is a natural choice as we use it in the UI. > > (2) When I double-click on an existing entry to open the editing panel, the > editing window comes up marked as "dirty", even though it's not. Again, > trivial, but ... > The window displays part of the document data, and the document is (apparently) dirty. In other words, this dirty state is a state of the document, not the item. This is standard behavior in document based Cocoa apps, in fact we don't even do anything to get it. > (3) Suppose I click "New" to create a new entry but then decide that's not > what I want to do. If I click the close button I get a dialog box with only > two choices, "Edit" and "Keep". I know this was discussed extensively, and I > don't want to revisit the whole discussion, but for the life of me I can't > understand why there's not a third choice, e.g. "Discard". Forcing the user > to save unwanted changes to a document is very unMac-like. Is there a way to > kill the editing panel without saving a new entry? > Yes, this has been discussed EXTENSIVELY and you can see the discussions on the archives of the mailing lists. I'm NOT going to keep repeating the many subtle pros and cons involved, let me just say that this has been thoroughly discussed. > With all that said, thanks for the great program. > > Chris You're welcome. Christiaan ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Bibdesk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bibdesk-users
