Reply to thread

Message

<blockquote data-quote="Micropolis" data-source="post: 824465" data-attributes="member: 96567">WorldWeather plugin v0.3.0 for MediaPortal v1.2.0 or higherDear community,a new build v0.3.3 was uploaded for testing purposes only, please use it at your own risk.List of plugin related changes:<ul>
<li data-xf-list-type="ul">new properties (#WorldWeather.LocationDate, #WorldWeather.LocationTime)</li>
<li data-xf-list-type="ul">configuration option to delete a profile</li>
<li data-xf-list-type="ul">rework and hardening of some weather wrapper routines</li>
</ul>From my point of view, this is a feature-complete build for the upcoming version 0.3.5. Now I'll start a complete regression test, maybe a debugged version or a release candidate comes after christmas.@bkv:It's hard to reproduce this issue on my development machine. I suspect some codepage issues here. I made some changes to the weather provider wrapper, please test the output with latest build. If this doesn't work again, I suggest to use the properties #WorldWeather.TodayWindSpeed and #WorldWeather.TodayWindDirection instead of #WorldWeather.TodayWind. Regarding weather coding description you can use #WorldWeather.TodayIconDescription or #WorldWeather.ForecastDay&lt;digit&gt;IconDescription alternatively. Please see the included manual for more information.@Cruzer:I don't know exactly, where I can start with analyzing. The whole content for time zones comes from managed .NET routines. During my test, I had select &quot;(UTC-08:00) Pacific Time&quot;, this gives me a UTCSpan result of -480 (and not -420 as you posted <a href="https://forum.team-mediaportal.com/823719-post488.html" target="_blank">here</a>). Could you tell me, which OS do you use and which .NET release do you have installed?Cheers, Micropolis</blockquote>

[QUOTE="Micropolis, post: 824465, member: 96567"] [b]WorldWeather plugin v0.3.0 for MediaPortal v1.2.0 or higher[/b] Dear community, a new build v0.3.3 was uploaded for testing purposes only, please use it at your own risk. [B]List of plugin related changes:[/B] [LIST] [*]new properties (#WorldWeather.LocationDate, #WorldWeather.LocationTime) [*]configuration option to delete a profile [*]rework and hardening of some weather wrapper routines [/LIST] From my point of view, this is a feature-complete build for the upcoming version 0.3.5. Now I'll start a complete regression test, maybe a debugged version or a release candidate comes after christmas. @bkv: It's hard to reproduce this issue on my development machine. I suspect some codepage issues here. I made some changes to the weather provider wrapper, please test the output with latest build. If this doesn't work again, I suggest to use the properties #WorldWeather.TodayWindSpeed and #WorldWeather.TodayWindDirection instead of #WorldWeather.TodayWind. Regarding weather coding description you can use #WorldWeather.TodayIconDescription or #WorldWeather.ForecastDay<digit>IconDescription alternatively. Please see the included manual for more information. @Cruzer: I don't know exactly, where I can start with analyzing. The whole content for time zones comes from managed .NET routines. During my test, I had select "(UTC-08:00) Pacific Time", this gives me a UTCSpan result of -480 (and not -420 as you posted [URL="https://forum.team-mediaportal.com/823719-post488.html"]here[/URL]). Could you tell me, which OS do you use and which .NET release do you have installed? Cheers, Micropolis [/QUOTE]

Verification