simplify
BDSKPubTypeString is considered a single valued group field and is supported in stringValueForKey
BDSKPubTypeString is considered a single valued group field and is supported in stringValueForKey
spacing
combine conditions
field action is always set for empty or single valued fields
citation fields are never inherited
correct check for adding to empty group
simplest check first
get possibly rebuild groups, they may have been reset due to inherited values
don't ask about changing inherited value when we would not need to change
return different field action when change is not needed as already applied
don't report ignoring changing inherited value when this was done because the value already applied
make oldValue local
just continue when ignoring overwriting inherited value
don't append to inherited value when nothing to append to
handle change to inherited values earlier
do not change inherited value for category group when the inherited value is changed in the parent
rename methods
pass old category group name to change rather than a copy of the old group
no return value which is meaningless and ignored
use variable for groups
make methods with withModDate: private, they are only used because of undo
don't duplicate title to booktitle in undo, this will be undone together
need only first item with dateAdded
method to mark items as new in bulk
set dateAdded and dateImported for script group items, unless it is a file which has dateAdded
use unique filename for empty filename rather than nil
rename and invert initializer parameter
initialize all ivars of BibItem
initialize all ivars of BibItem
pass nil as type for empty bibitem
shared method to get date added or modified from a field
methods to set cached year and month
use formattedDate accessor
update metadata explicitly in setPubFields:
should reset groups for year and month
initialize dates from initializers separately, don't call updateMetadataForKey:
use correct string constant
preserve date added in setPubFields: and set date modified, don't update in updateMetadataForKey:
combine some checks for field names
people and URLs don't use inherited values, so no need to reset
call parent directly
revert an earlier commit, we only set macroResolver when we already had a different one
we don't use complex strings for ISI group so no need to set macroResolver
string has nil macroResolver for default one
replace pub field value only when macroResolver is different
already did partial check for key
don't add localhost to missing file url with path
Update release notes
display path from bookmark data when resolving linked file URL fails
There were a bunch with just a date, no time, all the same: date-added = {2004-01-01} and otherwise with capitalized PM, such as this: date-added = {2026-10-24 2:53:06 PM +0200}
set standard locale to get month names
No, these should also be fixed, and I thought I did, the casing should not matter. Can you give an example of such a date? I replaced the test version again, this really should also interpret the dates that were added recently with the non-24-hour format.
don't bother trying to fix date strings that are clearly too short
first try to parse date strings with the current locale as we have used until now
delete characters instead of replace
revert previous commit
reuse variable
allow fixing standard description in NSDate category method
combine conditions and assinments
Yes, that version works! It shows the Added dates in my original bib file. At least it does for those that have presumably well formed dates in that file on a 24h clock. Newer references that I added in the last month are blank. Those have "AM" or "PM" in the time (uppercase). In a test file I made with "pm" (lowercase) the date showed in the column. But I can fix those references and I would say the problem is solved.
we already set the calendar
make sure we don't pass nil, use correct string
make sure we don't pass nil
fix edge case
a bit more lenient, in case dates are shorter
code alignment
I see what was going wrong, though I am rather surprised it stops doing anything. I replaced the test version (at the same location) with some better fixed. Could you try that?
fix correction to date string, time using am.pm can have single digit hour and 12 is an edge case
I tested it, but it could not open any .bib file - I didn't throw any error that I could see, but it didn't do anything. I could create a new bibliography, but that was unresponsive to adding a new bib file to it. I created an entry by hand, saved the file, and it couldn't read it back. The new saved file, however, did not show "am" in the time.
set locale and calendar for date formatter
set Gregorian calendar for daate formatting to be sure
I uploaded a test version at https://bibdesk.sourceforge.io/BibDesk.zip. Could you please download this and test it out to see if that fixes this issue?
fix the standard description of the date instead of trying current locale, as the latter can have changed.
try to parse date from standard description with current locale when standard format fails, apparently Apple now takes the format as a suggestion and may use am/pm times. Fix the dates when this happens.
I may have some idea where the bug comes from. The documentation mentions something very stupid (basically that they do it deliberately wrong, what we say there seems to be just a suggestion rather than an instruction). Although the documentation does not say so, perhaps Apple has now also introduced that deliberate bug on macOS. (Which would be a deliberate bug with an added documentation bug). I may be able to fix this (although I cannot test this myself). But the fix may make the dates added in...
set locale of dates with RFC3339 format to en_US_POSIX to make sure they are stable
That looks wrong. There should not be an am/pm, we explicitly tell the formatter to use a 24 hour format to be consistent and independent of your preferences. Apparently for you it depends on your preferences, which it definitely should not.
Yes, very weird and driving me crazy! I tried changing the date format in System settings. The format in the bib looks e.g like date-added = {2005-10-11 08:39:45 -0700} When I add a new item to the file, it shows today's date in the column, and this is saved in the bib file: date-added = {2026-10-24 5:36:35 pm +0200}, OK, so I just added "pm" to the old date (date-added = {2005-10-11 08:39:45 pm -0700} and it worked, so you might be right and that at some point in the past I had a 24h format
That sounds really weird. A difference I can think of is your preferences for the date format. We use your preference for the short date format. But I fond it hard to believe that this could go wrong. Perhaps there may also be a bug in parsing the date from the data, what format does the date have on your old items? And is the format different for newer items? Also, are you saying the problem does not occur for new items added, also when reopening the file? Or does it occur for any item in a file...
Blank Date-Added column
Full-screen scrolling leaks table row views; severe lag
Thank you; and you were right. To test your point, I built a minimal AppKit application that contains nothing but a view-based NSTableView of 5,772 rows and ten columns. It obtains row views through makeViewWithIdentifier:NSTableViewRowViewKey, exactly as BibDocument does, and cell views through makeViewWithIdentifier:owner:. It counts live row and cell views in init and deinit. In a normal window, a top-to-bottom scroll leaves 33–37 row views alive. In native full screen, a scroll of similar length...
This is really weird, and makes no sense to me. I really don't see how there can be anything different between full screen and normal view. The views in the table are managed by AppKit, we only tell it what to get. So this really sounds like an AppKit bug, and I really don't see how we could fix this, as we aren't getting involved.
Corrected text (the original paste garbled non-ASCII characters and two code blocks): Detailed Description Overview When a document window is in native macOS full screen, scrolling the main publications table does not recycle row views. Every row the table scrolls past remains alive: one BDSKColorRowView, plus one NSTableCellView per visible column. After one top-to-bottom pass through a 5,772-entry library: The process holds ~4,900 row views and ~49,000 cell views. Resident memory rises from ~0.3...
Full-screen scrolling leaks table row views; severe lag
redraw line number view when scrolling, somehow this is done only when scrolling bby more than a page
Cannot open normal files after opening an invalid file
Fixed for the next release
don't create error with nil underlying error
Cannot open normal files after opening an invalid file
use variable
Typst
Tag for release
Update version numbers for release
reorder for consistency
macros for keys