home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
MediaPortal 1 Plugins
WorldWeather plugin v1.10.0 for MediaPortal 1.3.0 and higher
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="michael_t" data-source="post: 956333" data-attributes="member: 85139"><p>Thank you for providing the sample mapping file. I tried to do my own icon mappings but got some strange results. Some examples (I disabled translation):</p><ul> <li data-xf-list-type="ul">Two different conditions for cloudiness (i think it was "cloudy" and "mostly cloudy") use the same icon though I mapped them to two different icons</li> <li data-xf-list-type="ul">The string "snow flurries" is displayed, but the online page of wetter.com does not tell anything about "snow flurries" (only of "light snow").</li> <li data-xf-list-type="ul">Though "snow flurries" is used as a display string, "snow_flurries" does not work in the mapping file for wetter.com (but it obviously works for other providers)</li> </ul><p>So I am a bit confused about how the weather conditions returned from the provider API calls are mapped to display strings ("snow flurries") and to icon mapping strings ("snow_flurries"). Do I misunderstand the logic of the mapping or is there a bug in this mapping for wetter.com?</p><p> </p><p>Michael</p><p> </p><p>PS: One improvement suggestion for the mapping file: It would be great if the file name in the mapping file could be a real string instead of only a number (e.g. "day_snow" would refer to the icon file "day_snow.png" like "14" now refers to the icon file "14.png"). This would be fully compatible with the old icon naming scheme but would allow speaking icon names.</p></blockquote><p></p>
[QUOTE="michael_t, post: 956333, member: 85139"] Thank you for providing the sample mapping file. I tried to do my own icon mappings but got some strange results. Some examples (I disabled translation): [LIST] [*]Two different conditions for cloudiness (i think it was "cloudy" and "mostly cloudy") use the same icon though I mapped them to two different icons [*]The string "snow flurries" is displayed, but the online page of wetter.com does not tell anything about "snow flurries" (only of "light snow"). [*]Though "snow flurries" is used as a display string, "snow_flurries" does not work in the mapping file for wetter.com (but it obviously works for other providers) [/LIST] So I am a bit confused about how the weather conditions returned from the provider API calls are mapped to display strings ("snow flurries") and to icon mapping strings ("snow_flurries"). Do I misunderstand the logic of the mapping or is there a bug in this mapping for wetter.com? Michael PS: One improvement suggestion for the mapping file: It would be great if the file name in the mapping file could be a real string instead of only a number (e.g. "day_snow" would refer to the icon file "day_snow.png" like "14" now refers to the icon file "14.png"). This would be fully compatible with the old icon naming scheme but would allow speaking icon names. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Plugins
WorldWeather plugin v1.10.0 for MediaPortal 1.3.0 and higher
Contact us
RSS
Top
Bottom