GNOME Bugzilla – Bug 629934
Month view defaults to Monday as start of week
Last modified: 2010-09-29 08:54:32 UTC
The Calendar view defaults to Monday as the start of the week, even though I set Sunday as the start of the week. I am using Evolution 2.30.3. When I set Sunday, the calendar reflects the change, until I close Evolution. The calendar resets itself to Monday as the start of the week and in the preferences, it still shows Sunday as the start of the week.
Is this about week view, or workweek view? (In general, exact steps are welcome, click by click, to reproduce)
Created attachment 170593 [details] Calendar Sceenshot
Created attachment 170594 [details] Screenshot of Preferences window.
This is in the Month view. Steps to reproduce: 1. Click the Calendar button at the bottom of the left menu, or press <CTRL + 3>. 2. View calendar in Month view. (See Attachment 1 [details].) 3. Click Edit -> Preferences. 4. Select Calendar and Tasks. 5. On the General tab, in the work week section, check to see if "Work week starts on" has Sunday selected. If not select it. (See Attachment 2 [details].) 6. Close the Preferences window. 7. If you selected Sunday for "Work week starts on", restart evolution. (At this time, Evolution calendar correctly displays Sunday as the start of the week in the Month view. If Sunday was already selected, the week still shows starting on Monday. 8. After restarting Evolution, view the Calendar again and it shows Monday as the start of the week.
*** Bug 624548 has been marked as a duplicate of this bug. ***
Created attachment 170756 [details] [review] evo patch for evolution; I recall I was fixing something similar, or saw something similar, I do not know when exactly, but that's not important. Here was done everything as expected, actual values were propagated from preferences, only the view was precalculated from default values, and not on value change.
(In reply to comment #6) > Created an attachment (id=170756) [details] [review] > evo patch > > for evolution; > > I recall I was fixing something similar, or saw something similar, I do not > know when exactly, but that's not important. Here was done everything as > expected, actual values were propagated from preferences, only the view was > precalculated from default values, and not on value change. I imaging the attachment for comment 6 is a patch... Dumb question... How do I apply the patch? Thanks.
(In reply to comment #7) > I imaging the attachment for comment 6 is a patch... Dumb question... How do > I apply the patch? Thanks. Yup, it's a patch :) Well, the answer is simple, it's a source file patch, thus if you compile evolution from sources, then you can apply it by $ patch -p1 <../evo.patch when staying in the evolution source directory and have saved the patch as evo.patch file in the parent directory of it. Though compiling evolution from sources is not that fun, so I suppose you are probably not doing that. It's usually easier to wait till it reaches sources itself and your distribution provides compiled version for you. Of course, you cannot test it for correctness in this case.
Thanks for the update. As I have the time, I will pull down the source, patch it, and recompile it. I run Fedora 13, x86_64 and sometimes patches are little slow to come out to the stable release. I'll let you know when I find once I have that done.
Okay, you have me there... Building Evo from source is going to be a pain. I hadn't realized that Evo was moved to git... (Not that familiar with git yet...) I think I'm going to end up waiting (I need to learn git and that whole thing). Grrr... Oh well. Again, thank you for your time invested. I would like to try it to ensure it works on my end. I'll keep working on the git repository stuff.
I have way to many dependencies to resolve, so I am going to have to wait.
Created commit 82f0d57 in evo master (2.33.1+) Created commit 0665e3e in evo gnome-2-32 (2.32.1+)