- March 24, 2009
- 98
- 26
- Home Country
- Norway
this requires some bigger architectural changes to the image cache functionality and isn't planned yet.... One "nice to have" option: If placeholders used but no new image found, please don't try to refresh last valid image...
as posted here before, the WorldWeather skin files are planned for the next Titan Extended update cycle. So maybe it's a good idea to take a look to the appropriate thread from time to time.Worldweather works with new MP beta 1.3.0.0 ?? I get an error : missing or invalid file: c:/programdata\teammediaportal\mediaportal\skin\titan\worldweather.xml
The solution would have been to read the documentation BEFORE installing. The documentation for the Titan skin says clearly that WorldWeather still is not supported (see here ). So you will have to wait for an update for the Titan skin.is there anyt solution ??
It seems that wetter.com had problems with my location parameters, but I have now manged to get most of them working. It took me a while to figure out that one has to eliminate the country prefix (e.g. AT-, CH-, GB-, NL-) with which wetter.com prefixes the postal codes in its web GUI in order for them to work as WorldWeather parameters. I still haven't been able to get weather forecasts from wetter.com for Geneva, Switzerland, despite using the name (Genf) and postal code (1200) returned by a search in the wetter.com web GUI. If anyone else has gotten forecasts from wetter.com to work for Geneva, I would be grateful for tips! (WorldWeather.xml attached).No rush, your new assignment is far more important. Meanwhile I have the pop-ups for wetter.com as well, so I suspect it's just a timing problem. I am increasing the waits and timeouts in "Expert Settings" from 30 to 60 seconds to see if that helps.
This was fixed with version 1.0.2 some days before.... 1. When I increase the "Timeout" value to more than 30 seconds, it gets stored correctly in MediaPortal.xml, but when I reopen WorldWeather configuration, it gets reset to 30 seconds (see attached screenshots)...
It's very simple to increase the maximum value, for example to 600. Is this ok?... 2. The plugin configuration GUI does not allow values > 60 seconds for "RefreshStartupDelay" and "RefreshResumeDelay"...
Longitude/Latitude values are needed to calculate sunset/sunrise time and other providers. You can take a look to the provider comparison sheet, which can be found in the manual.... 3. The plugin configuration GUI insists on having longitude and latitude values, even when they aren't needed (ISTR that they aren't used by wetter.com)...
Global configuration parameters are saved in mediaportal.xml, location specific configurations in worldweather.xml. This separation is required and useful.... I don't understand why the timing parameters are stored in MediaPortal.xml instead of in WorldWeather.xml. It confused me at first, because the stored values don't get updated until MP configuration is closed, whereas those in WorldWeather.xml can be updated from the GUI at will ...
That is not quite right, the new inbuilt plugin is a lite version with significantly fewer features. See our internal thread here for more information or Area 51 later.... and WorldWeather is on its way to becoming a built-in MP plugin...
I'm in discussion with our doc group to find a solution and to update the existing wiki pages. Please be patient.