Replies: 3 comments 6 replies
-
|
You're right that the #calendarRoot attribute is the key difference between how Journals and regular Collection/Calendar views handle events. In a regular calendar view (without #calendarRoot), you can create events with start/end dates and times, and they’ll display as timed or multi-day events, which you can drag and resize. In contrast, when #calendarRoot is present (as in Journals), the system expects each child note to represent a single day (using the #dateNote attribute), and all events are shown as all-day, regardless of any start/end time attributes. This design prevents multi-hour or multi-day events in Journals and disables interactive editing like dragging or resizing events reference. #calendarRoot and #workspaceCalendarRoot both mark a note hierarchy as a calendar root, enforcing this "day note" behavior. The difference between them is subtle and mostly internal, but both result in the same limitation: only day-level notes are shown, and time-specific events are ignored reference. If you remove #calendarRoot from a Journal, it would revert to regular calendar behavior, allowing timed events—but this breaks the Journal’s day-note structure and isn’t recommended unless you want to lose the Journal’s automatic day-note features. The table view shown in the docs is available in regular calendar views (set with #calendar:view=table), but not in Journals, because the Journal’s structure and #calendarRoot prevent the display of time-specific events as rows reference. If you want to manage timed events, create a separate Collection/Calendar view without #calendarRoot. Journals are best for daily notes, not for scheduling events with specific times. To reply, just mention @dosu. How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other |
Beta Was this translation helpful? Give feedback.
-
|
Does your calendar note have the attributes referenced in the Calendar documentation? Note that there is no Journal usage is covered in the documentation under Advanced Usage / Advanced Showcases / Day Notes. I believe that an attribute named "journal" would be more descriptive of the behaviour, and that the documentation should move its explanation to somewhere easier to locate. Also, check out dosubot's reply and the issue #6204 it references, as they provide further insight. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
-
If I create a note and set it to Collection and Calendar view I can add child notes with
startTimeandendTimeand they will be displayed on the calendar grid. However this does not work with the Journal. The documentation is unclear, it seems it's not possible to create multi-day or multi-hour events in the Journal.The docs show a table view which I have not been able to recreate, I can only modify the attributes to set start/end date/time
It looks like the culprit is the
#calendarRootattribute, (there is also#workspaceCalendarRootbut it's not explained what is the difference between the two). Why is this attribute needed? Can it be removed from the Journal? Can someone explain more in detail how calendars work?Beta Was this translation helpful? Give feedback.
All reactions