This beta further refines the mark/unmark/filtering labeling and functionality.
I’ve eliminated any reference to “hoisting,” since that was too confusing. Now it’s just “Mark/Unmark”.
And I’ve added a Filter option to show unmarked items, instead of marked items.
And also, in an unrelated action, I’ve changed the name of the “Transform” menu to “Odds”, as in “Odds and Sods” or “Odds and Ends.” My main motivation here was to take up a little less menu space. Any interested feedback on this change would be appreciated.
Notenik-19-0-4.zip (32.0 MB)
“Odds” - cute! Ultimately I prefer Transform because it tells me more about what to expect from the actions contained in the menu.
The fact that you’ve reached for “odds and sods” signals a more general issue that is developing. The menus are increasing in size. Your generosity with feature requests ( I can’t remember you ever saying no) creates a need to put the new thing somewhere and it may be an awkward fit. It may be time to think about re-organising the menu contents and organisation.
For example, some of the menu items are only applicable to a specific type of collection. They simply don’t do anything unless a specific field type is present. That’s very confusing for users (me). I’m not sure what’s involved with managing the menu display but having menus that reflect the state of possibility for the current collection would be a good goal. Dimming the menu items that aren’t going to be functional would assist us.
I expect it will be common for users to have several collections open at once and that they may vary considerably, so the menu switching would have to interrogate the template each time a window is loaded. That’s probably a pain to code for, but I’ve got an M2 Pro Silicon and it’s not going to blink at the workload. 
The mark / unmark is working really well. The use of “Mk” as default is clunky. The black flag is a much better default. You might offer a short selection as built-in options that we can choose in the general settings area because chasing down unicode decimal values isn’t everybody’s idea of fun.
Finally: Bug report for v19.0.4. The “Edit Collection Template” command is giving me the spinning pizza. Force quit is the only way to recover.
⚑
BLACK FLAG
2691
︎
FLAG IN HOLE
26F3
★
BLACK STAR
2605
✻
TEARDROP-SPOKED ASTERISK
273B
☛
BLACK RIGHT POINTING INDEX
261B
➼
WEDGE-TAILED RIGHTWARDS ARROW
27BC
●
BLACK CIRCLE
25CF
︎
BLACK MEDIUM SQUARE
25FC
✓
CHECK MARK
2713
The “Mark” contextual menu command in the List view marks only the current note while in the Outline view, it marks all descendants as well. This is a helpful improvement over the previous version in my opinion.
I found the following bug in 19.0.4:
- The “Show Unmarked Only” menu option seems to show all notes rather than just the unmarked notes, i.e., it acts like “Show All”
You are right - it behaves the same on my machine. “Show Unmarked Only” does not change the list at all. Starting from the “Show All” view, it shows the entire list, but starting from the “Show Marked Only” view, it still shows only the marked notes, i.e., it does not seem to change anything in the current view.
Thanks for testing and reporting, and sorry about the bugs! Try the latest beta when you get a chance. I think I’ve got things sorted now!
@Malcolm I appreciate your feedback about the menus. I’ll have to ponder all of this for a while before I can figure out what (if anything) to do about it. I have not been able to replicate the issue with the Edit Collection Template function. I wonder if anyone else is having similar issues?