-
Notifications
You must be signed in to change notification settings - Fork 339
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unset Default temperature unit #206
Comments
You seem to have temperature in Kelvin. Is that what you intended?
|
No, actually it was unset....? Just checked. 297 K is cold isn't it? |
No, it's 24 of Celsius
|
ya setting the value fixed it |
Unrelated did you just know that conversion or was some calculator involved ... I'm impressed |
That's in school program of physics 😉
|
Appears resolved, closing |
As @brarcher points out, this is not actually resolved. Suggestions what to do? |
I'm getting a similar issue with the default temperature being measured in Kelvin, but I'm getting "F" for my unit. Normally Fahrenheit is "°F". Is the unit being set based on locale or location? The alpha/char portion of the unit seems to be set to a decent default, save for the missing "°". It seems that whatever detection is being used to determine a default unit is not quite complete. Assuming that's intended behavior. |
Alright, so I cleared my app cache/config for Forcastie, force stopped it, and switched my system language to "English (United Kingdom)" from "English (United States)". Upon restarting the app I got my default location as "London, GB" with "C" as my units. Temperature is still in Kelvin. It seems part of the defaults are locale/system language based. |
@DerVerruckteFuchs I'm not sure how units are selected, I assumed it was by the user, ignoring locale |
show no indication that temperature units are selected by locale. |
martykan made some changes yesterday, they may have fixed the problem. If it builds OK, I may move v1.5 forward by 3 weeks, or more likely do a maintenance fix of v1.4.2 |
Closing, this will appear in v1.5 in a few days |
The text was updated successfully, but these errors were encountered: