asked 2015-06-15 13:00:15 +0300
I don't think this bug was already mentioned. I nearly missed an appointment today because of a weird bug in calendar, which apparently appears only when previous month ends on Sunday.
When I open calendar, today appears to be Tuesday instead of Monday. After moving to May then back to June, this error is fixed. Running 1.1.4.29.
PS: pardon my French...
answered 2015-06-15 17:09:08 +0300
I have same bug, and I think it's because of calendar patch. Try to uninstall this patch I did it and it works fine now. This bug appears although the patch isn't applied.
I trust you. However I dislike the calendar without column headers. I prefer to stay with the patch, keeping aware of the bug.
objectifnul ( 2015-06-15 17:41:06 +0300 )@objectifnul then it's not a bug. the patch make the bug. Please close your thread and make a feature one that bring the calendar to column, and report the bug to the patch-dev, who could adapt it in proper stand, until jolla decide to work on your feature request.
cemoi71 ( 2015-06-15 18:50:41 +0300 )answered 2015-06-16 02:57:28 +0300
I have uploaded updated v1.0.8 of the SailfishOS Calendar Patch to Openrepos.
This should fix the issue with not respecting Week starting on Monday Setting and displaying incorrectly when launching the app. It should follow the setting now. You may still need to close Calendar and restart it or swipe between months for some settings to take effect.
Thanks for the feedback. Enjoy!!
Asked: 2015-06-15 13:00:15 +0300
Seen: 509 times
Last updated: Jun 16 '15
I can confirm this behaviour too. Have you been using the calendar patch?
damourti ( 2015-06-15 15:53:53 +0300 )Bug can be reproduced with and without calendar patches applied.
objectifnul ( 2015-06-15 16:01:40 +0300 )I have the feeling that this bug came with the patch, but not sure, I will ask the patch developper
damourti ( 2015-06-15 16:09:07 +0300 )Mmm. Not sure the patch can be incriminated, as the bug also appears when no patch is applied.
objectifnul ( 2015-06-15 16:16:55 +0300 )@objectifnul : This issue is now reported internally. Thanks for spotting and reporting it :)
Nazanin ( 2015-06-15 17:01:49 +0300 )