You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a note's "Editable" property is set to readonly, your FindWidget does not respond to theCtr+F shortcut at all (which I don't blame you for), but if its "Editable" property is set to "Auto" and it is so long that Trilium puts it into readonly mode automatically, your FindWidget does show up upon pressing Ctrl+F but it does not show any search results, which may confuse users.
I tried to find a specific segment in a very long set of lecture notes this way and was surprised that while Trilium's global search bar has picked up the relevant keyword but your FindWidget did not show any search results in the corresponding note. I began to think I was crazy until I noticed it was just a bug.
The text was updated successfully, but these errors were encountered:
Thanks, Trilium doesn't have a consistent check for readonly notes so the findwidget only disables itself on "statically" readonly notes, not on "dynamically" readonly notes which is the "auto" case you point out.
I'm leaving this open and I'll either implement a runtime check for dynamically readonly or implement the findwidget in readonly notes in general.
When a note's "Editable" property is set to readonly, your FindWidget does not respond to theCtr+F shortcut at all (which I don't blame you for), but if its "Editable" property is set to "Auto" and it is so long that Trilium puts it into readonly mode automatically, your FindWidget does show up upon pressing Ctrl+F but it does not show any search results, which may confuse users.
I tried to find a specific segment in a very long set of lecture notes this way and was surprised that while Trilium's global search bar has picked up the relevant keyword but your FindWidget did not show any search results in the corresponding note. I began to think I was crazy until I noticed it was just a bug.
The text was updated successfully, but these errors were encountered: