-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
James Tabor wrote: | Hi all! | | Missing scroll bars for timezone.
Also, it's a VERY small box (3 can be seen at once), which makes it very annoying if your in a zone that's far away from the ROS (And Windows default of Tijuana (And Redmond)) default. Some version of Windows to it this way and it's ANNOYING. I strongly suggest a much larger (10 viewable at a time, maybe) box for this.
~ -uniQ
PS. Also, why use the Windows default of Redmonds timezone? Why not something like, like the area in which the selected language is the most predominant?
On Fri, 26 Nov 2004 20:54:10 -0500, K McI uniq@wwsvr.bounceme.net wrote:
PS. Also, why use the Windows default of Redmonds timezone? Why not something like, like the area in which the selected language is the most predominant?
I don't mind the Windows default... I am in the Pacific Time Zone (Seattle) :P
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Mike Swanson wrote: | I don't mind the Windows default... I am in the Pacific Time Zone (Seattle) :P
But say you're in Germany. If you've previously told ROS that you speak German, wouldn't it make sense to default to whatever timezone Germany is in? (Windows may already do this, I don't know)
~ -uniQ
K McI wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Mike Swanson wrote: | I don't mind the Windows default... I am in the Pacific Time Zone (Seattle) :P
But say you're in Germany. If you've previously told ROS that you speak German, wouldn't it make sense to default to whatever timezone Germany is in? (Windows may already do this, I don't know)
~ -uniQ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBqNog7mze81O92HkRAm2RAJ48qVPC+/oc/AqmR75S7lLjqjWORgCfQEAA T3ywMtuCtxoOYgtROhqJhIE= =PDtT -----END PGP SIGNATURE----- _______________________________________________ Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
While it makes sense, windows does not already do this.
Adam Babcock wrote:
K McI wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Mike Swanson wrote: | I don't mind the Windows default... I am in the Pacific Time Zone (Seattle) :P
But say you're in Germany. If you've previously told ROS that you speak German, wouldn't it make sense to default to whatever timezone Germany is in? (Windows may already do this, I don't know)
While it makes sense, windows does not already do this.
I don't think that's a valid assumption. Many of us choose French as default language, but we wouldn't want to be placed in the France timezone. Of course, Windows does ask for "Location", and it should at least use that for a timezone guess, but the language selection shouldn't be a factory, imo. Unless you want to get into bloated code such as if (Location == CANADA && Language == FR) Timezone = Quebec.
Then again, choosing Seattle isn't better either. I would just start with GMT as default. Makes everyone happy.
Best regards, Alex Ionescu
Alex Ionescu wrote:
Adam Babcock wrote:
K McI wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Mike Swanson wrote: | I don't mind the Windows default... I am in the Pacific Time Zone (Seattle) :P
But say you're in Germany. If you've previously told ROS that you speak German, wouldn't it make sense to default to whatever timezone Germany is in? (Windows may already do this, I don't know)
While it makes sense, windows does not already do this.
I don't think that's a valid assumption. Many of us choose French as default language, but we wouldn't want to be placed in the France timezone. Of course, Windows does ask for "Location", and it should at least use that for a timezone guess, but the language selection shouldn't be a factory, imo. Unless you want to get into bloated code such as if (Location == CANADA && Language == FR) Timezone = Quebec.
Then again, choosing Seattle isn't better either. I would just start with GMT as default. Makes everyone happy.
Best regards, Alex Ionescu _______________________________________________ Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
As I also live in Montreal, I can't believe I didn't think about that. Having ROS select a default timezone based on location also would not work, even your example based on location and language, for example, there are a large number of French speaking people living in Alberta. Perhaps starting with GMT would be the best for a default.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Alex Ionescu wrote: | As I also live in Montreal, I can't believe I didn't think about that. | Having ROS select a default timezone based on location also would not | work, even your example based on location and language, for example, | there are a large number of French speaking people living in Alberta. | Perhaps starting with GMT would be the best for a default.
Isn't the code for French in Canada different then the one in France, like fr-CA and fr-FR? Or are they both the same?
~ -uniQ
K McI wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Alex Ionescu wrote: | As I also live in Montreal, I can't believe I didn't think about that. | Having ROS select a default timezone based on location also would not | work, even your example based on location and language, for example, | there are a large number of French speaking people living in Alberta. | Perhaps starting with GMT would be the best for a default.
Isn't the code for French in Canada different then the one in France, like fr-CA and fr-FR? Or are they both the same?
~ -uniQ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBqObC7mze81O92HkRAoHBAJ9CXzGpfgtmYDDE8EgpFMxwqj5UfwCfQzIn FhgqMxEk2FT9KZyHlIjiAAk= =qDca -----END PGP SIGNATURE----- _______________________________________________ Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
They are different, but that doesn't change the fact that French in Quebec is not the same as French in Alberta or anywhere else in Canada, and the timezone difference is huge.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Adam Babcock wrote: | They are different, but that doesn't change the fact that French in | Quebec is not the same as French in Alberta or anywhere else in Canada, | and the timezone difference is huge.
The point is, if you pick the fr-CA one, it should change to the Quebec zone, not the French one.
~ -uniQ
K McI wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Adam Babcock wrote: | They are different, but that doesn't change the fact that French in | Quebec is not the same as French in Alberta or anywhere else in Canada, | and the timezone difference is huge.
The point is, if you pick the fr-CA one, it should change to the Quebec zone, not the French one.
The point is you might be a French Canadian living in Alberta.
Best regards, Alex Ionescu
Adam Babcock wrote:
As I also live in Montreal, I can't believe I didn't think about that. Having ROS select a default timezone based on location also would not work, even your example based on location and language, for example, there are a large number of French speaking people living in Alberta. Perhaps starting with GMT would be the best for a default.
Please don't overquote 2 different ML Footers + a whole PGP Signature. Some of our readers are on 56K modems and it also makes reading through replies much more tedious.
I hope you've finished the math module..
Best regards, Alex Ionescu
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Alex Ionescu wrote: | Please don't overquote 2 different ML Footers + a whole PGP Signature. | Some of our readers are on 56K modems and it also makes reading through | replies much more tedious. | | I hope you've finished the math module.. | | Best regards, | Alex Ionescu
Err, was that quoting business aimed @ me or Adam?
~ -uniQ
PS. I'll admit that my idea has some problems with it, but I was just railing @ the fact that someone who is not very likely to live in the same zone as Redmond would have to correct ROS/Windows every time they installed. I admit that my method might result in being some zones off, but @least it's trying to be intelligent, instead of just assuming that everyone lives in GMT -8.
K McI wrote:,
Err, was that quoting business aimed @ me or Adam?
Adam.
PS. I'll admit that my idea has some problems with it, but I was just railing @ the fact that someone who is not very likely to live in the same zone as Redmond would have to correct ROS/Windows every time they installed.
But it's just as false of an assumption as any other to base it on location/language.
I admit that my method might result in being some zones off, but@least it's trying to be intelligent, instead of just assuming that everyone lives in GMT -8.
The most intelligent solution is to stick to GMT 0.
Best regards, Alex Ionescu
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Alex Ionescu wrote: |> PS. I'll admit that my idea has some problems with it, but I was just |> railing @ the fact that someone who is not very likely to live in the |> same zone as Redmond would have to correct ROS/Windows every time they |> installed. | | | But it's just as false of an assumption as any other to base it on | location/language.
Wait, aren't location and timezones the SAME thing, or at least based off of the other?
|> I admit that my method might result in being some zones off, but |> @least |> it's trying to be intelligent, instead of just assuming that everyone |> lives in GMT -8. | | | The most intelligent solution is to stick to GMT 0.
Then we might as well keep it @ GMT -8
~ -uniQ
K McI wrote:
Err, was that quoting business aimed @ me or Adam?
PS. I'll admit that my idea has some problems with it, but I was just railing @ the fact that someone who is not very likely to live in the same zone as Redmond would have to correct ROS/Windows every time they installed. I admit that my method might result in being some zones off, but @least it's trying to be intelligent, instead of just assuming that everyone lives in GMT -8.
I am pretty sure that was aimed at me, my bad, sorry about that Alex. I didn't realize that it was you, forgot that you are a developer, and yes, I finished the math module, well, sort of...{read -> I'll do it tonight ;)} As for the timezone, I agree with you K McI that it should intelligently pick the timezone, but I think it is just too difficult, especially with very metropolitain nations such as Canada. I suggest one of two things: 1) Stick with GMT as a default 2) Pick some neutral default considered the "home" of ROS, I believe Windows defaults to GMT -8 because of the location of Microsoft HQ {Redmond, Washington}
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Adam Babcock wrote: | As for the timezone, I agree with you K McI that it should intelligently | pick the timezone, but I think it is just too difficult, especially with | very metropolitain nations such as Canada.
While attempting to guess the location isn't going to be successful 100% of the time, it would probably be better then the 99% incorrect that you get with always defaulting to 1 set zone.
Also, are there any other user-set preferences that come before the date/time page (How do you call the different parts of Setup?) that might help determining location?
~ -uniQ
PS. Thought into the future, but if we get update/download mirrors, could we do those by timezone or vice versa?
"K McI" uniq@wwsvr.bounceme.net wrote:
Also, it's a VERY small box (3 can be seen at once), which makes it very annoying if your in a zone that's far away from the ROS (And Windows default of Tijuana (And Redmond)) default. Some version of Windows to it this way and it's ANNOYING. I strongly suggest a much larger (10 viewable at a time, maybe) box for this.
Ok, I'll make the timezone combobox a bit larger and use a different default timezone for the US.
Regards, Eric
"James Tabor" jimtabor@adsl-64-217-116-74.dsl.hstntx.swbell.net wrote:
Missing scroll bars for timezone.
This is a bug in the combobox control but no bug in the syssetup dll.
Regards, Eric
-
Adam Babcock -
Alex Ionescu -
eric.kohl＠t-online.de -
James Tabor -
K McI -
Mike Swanson