Saturday, January 1st, should be week 0, as the MSDN states (in the documentation for the Calendar Control) that week 1 is the first week of the year with 4 days in it. But Windows 7 appears to want to call it week 1. Which (of course) throws off the week numbering for the entire year.-Stoic Joker (January 16, 2011, 04:37 PM)
Has anyone else heard of, or ran across this bizarre behavior?-Stoic Joker (January 16, 2011, 04:37 PM)
Can you post some code (or be quite specific about the Calendar control/class you're using)?-mwb1100 (January 17, 2011, 02:12 AM)
The question at this point, is if I add an option to adjust wr975's iFirstWeekOfYear registry entry ... Will that create a potential problem for other applications running on the user's machine?? (e.g. Sure it's easy as hell to do, but should it be done?)
*Shrug* ...7 is broken?-Stoic Joker (January 17, 2011, 05:19 PM)
iFirstWeekOfYear = "Specifies which week of the year is considered first.
0 - Week containing January 1 is the first week of the year.
1 - First full week following January 1 is the first week of the year.
2 - First week containing at least four days is the first week of the year."
I was in the process of arriving at that conclusion also ... As I too was Googling ... But decided I'd googled enough, when I realized that I'd been steadily (but unconsciously) swearing in Bavarian for over half an hour. :huh:The question at this point, is if I add an option to adjust wr975's iFirstWeekOfYear registry entry ... Will that create a potential problem for other applications running on the user's machine?? (e.g. Sure it's easy as hell to do, but should it be done?)
*Shrug* ...7 is broken?-Stoic Joker (January 17, 2011, 05:19 PM)
Probably not, because if an (European) user wants the ISO week number, then it should be set to "2" anyway. (I've googled a bit)-wr975 (January 18, 2011, 05:25 AM)
iFirstWeekOfYear = "Specifies which week of the year is considered first.
0 - Week containing January 1 is the first week of the year.
1 - First full week following January 1 is the first week of the year.
2 - First week containing at least four days is the first week of the year."
On Win XP this registry setting seems to be ignored. So... is XP broken ? ;D-wr975 (January 18, 2011, 05:25 AM)
This sounds the same as a bug in VB5 I submitted to Microsoft, a couple of eons back. The problem isn't with the OS, but with the library.Interesting, but this is a pure C project, using the Windows Common Controls - so there is no additional runtime library to speak of - Not to mention the behavioral change between OS's ... But I'm with you in spirit. :)-CWuestefeld (January 18, 2011, 11:10 AM)
In some years, the end of the last week of the old year extends into Jan 1, Jan 2, etc. If you ask about the week # with respect to the old year, you get the right answer (that it's wk 53 or whatever). But if you ask that same question with respect to the new year (i.e., "what's the week number for Jan1, 2011"), then it assumes that it's part of the new year, without considering that it might be the old year's dying days.One of the first things I discovered when I started down the add week numbers to the project path ... Was that the only thing that week numbering did consistently, according to the ISO standard, was change... Sure for the most part they have it down to the three most likely suspects. But they don't always fit into the regional(ization) borders because of the multitude of who likes what where combinations. There are actually 3 areas (globally speaking/I forget the country names), that require that you basically wing-it week number wise.-CWuestefeld (January 18, 2011, 11:10 AM)
Microsoft said that this was the intended behavior, and declined to fix it. :huh:-CWuestefeld (January 18, 2011, 11:10 AM)
@f0dder:...and there's plenty of examples of code that works on Win9x but breaks on WinNT, or works on Win2000 but breaks on WinXP (et cetera), because developers of said software made assumptions that violate the specs...
Because these apps do not experience problems on Vista and 2008 R1 operating systems. Which is what makes me say that Windows is (unintentionally?) breaking things.-Shades (January 18, 2011, 10:30 AM)
@f0dder:Aw shit, I was rather enjoying that discussion too...
Being not too proud to admit I could be wrong in my assumptions or logic, I will agree with you. Let's also stop pulling the thread off-topic.-Shades (January 18, 2011, 10:49 PM)
@Stoic Joker:[/quote]
Indeed, it is/was my frustration speaking. Sorry about that.-Shades (January 18, 2011, 10:49 PM)