CintaNotes Developer wrote:...I'm not sure about conflicting tags. Probably it would be better to display an error message and not allow assigning tag/changing tag property?
I would never forbid the user from assigning a tag (or other value) they wanted to assign. That's just asking for complaints. Instead, you might consider visual feedback. Maybe make the tags an alert color - like red or underline them - to indicate they might be conflicting, but allow the user to assign them anyway. It just isn't safe to assume that a note would never need to assign conflicting tags. For example, an article I'm working on about a bash shell function has code in it that shouldn't wrap, but I prefer my articles to wrap so I don't have to 'end-jump' to complete my sentences. It's tagged with both 'articles' (allows wrapping) and 'bash' (no wrapping) in the same note, I would expect that the tags wouldn't be forbidden, but at the same time, I'd like to selectively decide in *this* fringe case whether to allow wrapping on a note-specific level. As a rule, though, the second I add 'articles' I want it to enable wrapping and (almost) never enable wrapping otherwise.
I would rather have the wrapping toggle button (the one by the title bar) display a question mark or something to indicate that it's in conflict mode, defaulting to the global policy.
The rules should be in the following order of precedence (highest to lowest):
1) individual note assignment (never propagated)
2) tag conflicts = global preference
3) tag-based preference (propagated for all notes with specified tags)
4) global preference