The row dates changes fixes up inconsistencies between file formats. It was that .bike would write row dates, while .md would not. Now all formats are treated the same:
- Default is don’t include dates. Unless they are actually needed that add a lot of clutter to files and are the most expensive part of file parsing.
- Setting is per document. Use File > Document Options to date serialization per document. There is not a persistent metadata flag for this setting. Instead when Bike reads a file it enables date writing if any read row contains a date attribute. Your existing documents that were tracking dates should continue to do so.
- You can change the default for new documents in Settings > Document. There is a checkbox after the file format. The setting is per file format, so you can, for example, have bike documents track, while markdown documents do not.
I’ve also made a bunch of changes to Settings > Extension > Calendar. By default calendars are now rooted at document root (instead of Calendar row). And they build Year/Month/Day structure using plain rows. You can now make this structure flatter, by unchecking levels in settings. You can also configure so that heading rows, or other text/formatting is inserted per level when rows are created.
Last, if you don’t want your calendar at root level, you can just move the structure to some other location in your outline. When new rows are needed the calendar builds off existing structure where it is located.
Fixed some problems with the last release and now we have 284
For me, the calendar extension in 284 seems to do this:
In other words, it ignores the numbers and just enters the ISO date syntax. I have not yet touched the settings. Is this expected or could this be a bug?
I think this now works the way it should!