When using some of the new Seq Field Formatting, the Edit tab will now allow entry/modification of the Seq field using either the raw value (n.n.n.n) or the formatted value. Changes in either will be immediately reflected in the other.
I’ve added some additional Log messages to help us figure out what’s going on with the missing iCloud container.
I thought it would be useful to reply here. This is the updated log.
iCloud Notenik container could not be found at /Users/-----/Library/Mobile Documents/iCloud~com~powersurgepub~notenik~shared/Documents?
Attempt to create iCloud container for Notenik threw an error: Error Domain=NSCocoaErrorDomain Code=513 “You don’t have permission to save the file “Documents” in the folder “iCloud~com~powersurgepub~notenik~shared”.” UserInfo={NSFilePath=/Users/-----/Library/Mobile Documents/iCloud~com~powersurgepub~notenik~shared/Documents, NSURL=file:///Users/-----/Library/Mobile%20Documents/iCloud~com~powersurgepub~notenik~shared/Documents, NSUnderlyingError=0x600003d19770 {Error Domain=NSPOSIXErrorDomain Code=13 “Permission denied”}}
iCloud Notenik Documents container available at /Users/-----/Library/Mobile Documents/iCloud~com~powersurgepub~notenik~shared/Documents? false
Error reading contents of iCloud drive folder
Could not create a new directory at /Users/-----/Library/Mobile Documents/iCloud~com~powersurgepub~notenik~shared/Documents/Starter Packs
Well, something strange is going on, but I’m sorry to say I’m not sure what. I just deleted my Notenik folder from my own iCloud drive and then, as soon as I launched Notenik, it was recreated for me. The error you’re getting is that you don’t have permission to create the folder, but I’m not sure why you wouldn’t have permission to create a folder for Notenik in your own iCloud Drive. Have you tried creating it manually? Just create a folder named Notenik on your iCloud Drive?
The outline tab uses the unformatted seq field, but I suppose if someone uses the formatted seq, it should give precedence to this?
The outline tab actually uses the formatted seq field, but it uses the “scoped” seq for the appropriate level.
For example, here’s what the Seq line looks like within the current beta Knowledge Base:
Seq: <seq: A.n.a.i.n|A.|xn.|xxa.|xxxi.|xxxxn.>
And see below for the resulting display on the Outline tab.
With the indenting, and the disclosure triangles, I actually think seeing this “abbreviated” (but still formatted!) Seq field looks better than repeating all the levels on every line!
@jvet93 Here’s another thought: Notenik has a Grant Folder Access option beneath the File menu. What if you use this and select your entire iCloud folder, before attempting to create a collection within iCloud?
Re: outline tab – ah, that makes sense, yes! I only had been using nanana for formatted seq, so I thought this would be used for the abbreviated version, too.
@benwf Part of the overall design philosophy of Notenik is to allow the user easy access to all of the bits and bobs going on under the hood. It aims to be more like one of the older cars where anyone could crack the hood on Saturday and start fiddling about, as opposed to one of the newer cars for which you have to have a license just to peer into the engine compartment.
So for this reason, if for no other, I have a preference for showing the user the underlying Seq value, as well as the formatted value.
But allowing them to edit either value was a really cool idea, and I’m happy with the way it’s turned out.
Also, I’ve implemented a bit of a failsafe mechanism: if Notenik tries to convert a raw Seq value to a formatted value, it then (behind the scenes) tries to convert the formatted value back to the raw value. If the result does not match the original, then the Edit tab will not allow access to edit the formatted value.
This would be kind of scary for me. Since the formatted field is a derived field, its appearance could change at any time, with a tweak to the template file. For everything else we are talking about, this would be seamless. But what to do about filenames? Try to rename every file in the Collection? And what if this were to result in a collision, with two files now having the same name? Renaming one file at a time is manageable, but a global rename might easily go astray.
Oh, totally understandable! I think this is probably due to perspective and its respective demands. If you work with a formatted representation of the sequence (like in outlines, e.g., for a book), it’s because the numbered sequence is what “automatically sequentially drives” the progress. Alternatively, if the sequence number itself is what you work with (e.g., Zettelkasten), it’s because that’s what you work “upon,” e.g., through linking, explicitly following up, etc.
So for the file naming, practically speaking, it would only work if the sequence ID is unique and the file name has at least the sequence ID in its name. (This is probably what Notenik does via its timestamps metadata instead.) And yes, I share the sentiment about crashing renaming large number of files—been there, done that
And last but not least: The new version just released should now place the user on the List tab after a collection reload, including one performed behind the scenes following some other significant collection action.
