Another beta is available, with two additional changes.
Blank Line Following YAML
When using YAML frontmatter, Notenik will now write a blank line following the end of the YAML metadata, and before the body of the note.
Incrementing Seq Values for New Notes
If you have elected to Change Note ID Configuration for your collection, and you have chosen the Seq field as your auxiliary value, and have opted to identify notes based on their aux field only, wtihout reference to the Title field, then a new Note’s seq will now be incremented just beyond the highest seq value yet used in the collection, without reference to the currently selected Note.
Also, the auto-incrementing really enhances my workflow. While testing, I noticed that after creating a new note but not doing anything, e.g., immediately clicking on another note, the note still gets created on the file system but won’t be shown in the list. While surely an edge case, unless the collection is reloaded or the app is restarted, this could lead to unintended gaps or follow-ups, as another new note will have an increased sequence number: say I created seq. 100, immediately switched instead of editing, creating another new note, which will then have seq. 101 assigned.
I don’t have a real suggestion for that, but my hunch would be maybe an option to have unedited new notes simply discarded. Talking about unexpected added complexities.
Check out the latest beta, which should fix this problem.
The fix is to save the note and refresh the display(s), so the new note is visible.
(I’d had a previous complaint about a user’s input simply being discarded when something like this happens, so Notenik was modified some time ago to save the in-progress note, even if the user has not explicitly requested a save.)
Thanks for reporting this. I think I’d seen some similar behavior myself, but hadn’t taken the time to track it down before now.
I believe something similar would also have happened if the user was changing key fields of an existing note.
This makes sense, thanks for the explanation! As always, thanks for the quick fix! Alas, I’m not at home until Thursday to test this, but I’ll let you know then
