I'm not sure what if you're reporting something broken or not. The "converted temps" shown in the status bar should show the other temperature scale values when you hover over certain parts of the GUI. For instance, if you have metric units chosen, your main GUI will show values in Celsius, km/h, millibars, etc. If you hover those values, the values shown in the statusbar will be imperial values. I added it as an easy way to see converted values without having to constantly change the actual setting back and forth. Make sense?Midas wrote:"Feels like" unit problem is solved -- imperial temperature measures still display in status bar with clear indication of "converted".
This feature uses a different site's API but it seems to work fine for me. What is the format mask string you're using?Midas wrote:The "LocalTime=1" doesn't break the main dialog anymore -- what it does is show the (almost) literal date format mask in the title bar.
This is another change I made and now is shows what Yahoo! sends back in the API. Beforehand, I used a different API value, "lastBuildDate," and now I use "Title." With the lastBuildDate value, it just updated the time to whenever the data was refreshed regardless of what time the actual weather data was generated. I think the Title value is the more accurate value. As for the WEST/CEST/EEST part, it's just displaying what the API returns.Midas wrote:Displayed time formats unchanged: e.g., "Conditions for Lisbon, Lisbon, PT at 10:00 AM WEST" in status bar -- WEST is confusingly Western European Standard Time, as opposed to CEST and EEST...
Yeah, probably placebo. It seems quicker for me today as well. *shrug*Midas wrote:Overall, sWeather seems snappier. Placebo?
With the new API changes, I have to use the Yahoo! console and YQL (Yahoo! Query Language) calls. For the weather data, I know that the Yahoo! console aggregates the data from the Weather Channel website and, possibly, a few other sources. What I'm getting at is Yahoo! are at the whim of the other sites it aggregates from. So, when it seems slower, it makes me wonder if Yahoo! are being rate-limited or other issues are at play. I'm just hypothesizing; I really don't know for sure.