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
I searched for existing Bug Reports and found no similar reports.
Expected Behavior
When selecting a "current date" in the settings, the calendar's "today" tooltip should display the correct date, and the Month setting should display the "current" month.
Current behaviour
When selecting a "current date" ibn the settings, the calendar's "today" tooltip displays the following month (eg: if the "current date" month is 3, the tooltip shows 4), and the Month setting displays the month immediately following the "current date" month.
Reproduction
Launch Obsidian, etc.
Open Settings > Community Plugins > Calendarium
Select custom calendar > Open Custom Creator
Select Dates > Current Date
Enter a current date
Close Calendarium settings
Close Obsidian Settings
Open Calendarium view in the sidebar
Hover over "today" = tooltip shows Current Date setting but for the month following the month selected in step 5
NOTE: My custom calendar has two intercalary "leap" months, one at the beginning of the year and one in the middle of the year. The first appears every seven years if the year is an odd number. The second, every seven years if the year is an even number. I believe what's happening is the Current Date setting is counting all months, including intercalary months.
Which Operating Systems are you using?
Android
iPhone/iPad
Linux
macOS
Windows
Obsidian Version Check
1.7.1 and 1.4.13
Plugin Version
1.4.0
Confirmation
I have disabled all other plugins and the issue still persists.
Possible solution
The Current Date setting should be "smart" enough to consider if the year includes a leap month or leap days and compensate as applicable.
No response
The text was updated successfully, but these errors were encountered:
for me the month in the hover is correct, but the year is not in sync with the displayed year of the calendar.
e.g. Today is 2022-09-11, but month calendar shows September 2023.
Double-clicking a date opens up a new calendar which shows that date... but the year is in sync with the Today hover year.
The calendar is configured with the years 2022, 2023, and 2024. But 2022 shows up as undefined.
Adding the following as a comment on the existing bug report because I think it's the same issue:
When an fc-date property is assigned to a note and the calendar associated is a custom calendar (eg: 394-15-09 00:19), that note shows on the correct month and date in the Calendarium sidebar view... however, clicking on that date to open an Agenda view shows the calendar for a month two previous from the correct one (to use regular months: if the date is 2024-09-18, it shows the Agenda view for 2024-07, with the correct day.
Check for existing bug reports before submitting.
Expected Behavior
When selecting a "current date" in the settings, the calendar's "today" tooltip should display the correct date, and the Month setting should display the "current" month.
Current behaviour
When selecting a "current date" ibn the settings, the calendar's "today" tooltip displays the following month (eg: if the "current date" month is 3, the tooltip shows 4), and the Month setting displays the month immediately following the "current date" month.
Reproduction
NOTE: My custom calendar has two intercalary "leap" months, one at the beginning of the year and one in the middle of the year. The first appears every seven years if the year is an odd number. The second, every seven years if the year is an even number. I believe what's happening is the Current Date setting is counting all months, including intercalary months.
Which Operating Systems are you using?
Obsidian Version Check
1.7.1 and 1.4.13
Plugin Version
1.4.0
Confirmation
Possible solution
The Current Date setting should be "smart" enough to consider if the year includes a leap month or leap days and compensate as applicable.
No response
The text was updated successfully, but these errors were encountered: