I have added .inc files for up to 15 days of "Pollen forecasts"
WeatherComJSONPollen.inc
WeatherComJSONPollen10Day.inc
WeatherComJSONPollen7Day.inc
WeatherComJSONPollen5Day.inc
WeatherComJSONPollen3Day.inc
This forecasts values for Grass / Tree / Ragweed pollen levels.
I also corrected an issue with WeatherComJSONAlerts.inc that would produce an error in the log if there were no current alerts on the site.
Get the new .rmskin in the first post of this tread.
It is currently October 13th, 2024, 6:30 am
⭐ Weather.com
-
- Developer
- Posts: 22851
- Joined: April 19th, 2009, 11:02 pm
- Location: Fort Hunt, Virginia, USA
-
- Posts: 442
- Joined: July 30th, 2014, 10:30 am
Re: ⭐ Weather.com
You've made a small mistake in your WeatherComCodes.ini skin starting from [MeasureLatitude6] on, where the StringIndex values of [MeasureLatitudeN] are assigned to [MeasureLongitudeN] and vice versa.
-
- Developer
- Posts: 22851
- Joined: April 19th, 2009, 11:02 pm
- Location: Fort Hunt, Virginia, USA
Re: ⭐ Weather.com
Thanks. That will be fixed the next time I release the .rmskin.pul53dr1v3r wrote: ↑August 5th, 2020, 9:58 pm You've made a small mistake in your WeatherComCodes.ini skin starting from [MeasureLatitude6] on, where the StringIndex values of [MeasureLatitudeN] are assigned to [MeasureLongitudeN] and vice versa.
-
- Posts: 78
- Joined: April 7th, 2010, 2:34 pm
Re: ⭐ Weather.com
I'm getting these errors with the Pollen JSON files.
Tried the Current and 7Part files.
Tried the Current and 7Part files.
You do not have the required permissions to view the files attached to this post.
-
- Posts: 16
- Joined: April 20th, 2020, 8:15 pm
Re: ⭐ Weather.com
Ever since V3 version of the JSON code update, when there's a weather alert (exclamation point), I get this when I click on it.
Si hoc legere scis nimium eruditionis habes. Fac ut vivas.
-
- Developer
- Posts: 22851
- Joined: April 19th, 2009, 11:02 pm
- Location: Fort Hunt, Virginia, USA
Re: ⭐ Weather.com
Try editing the skin .ini file and finding this meter:TheRealDjElite wrote: ↑October 26th, 2020, 5:58 pm Ever since V3 version of the JSON code update, when there's a weather alert (exclamation point), I get this when I click on it.
Code: Select all
[MeterAlert]
Meter=Image
X=10
Y=7
W=30
H=30
ImagePath=#ImagePath#\Alerts
LeftMouseUpAction=[https://weather.com/weather/today/l/#Latitude#,#Longitude#]
ToolTipType=1
ToolTipTitle=#AlertsTipTitle#
ToolTipText=#AlertsTipText#
Hidden=1
-
- Posts: 16
- Joined: April 20th, 2020, 8:15 pm
Re: ⭐ Weather.com
Thanks. It worked. I replaced the old "LeftMouseUpAction" command.jsmorley wrote: ↑October 26th, 2020, 6:09 pm Try editing the skin .ini file and finding this meter:
Be sure the LeftMouseUpAction looks like that...Code: Select all
[MeterAlert] Meter=Image X=10 Y=7 W=30 H=30 ImagePath=#ImagePath#\Alerts LeftMouseUpAction=[https://weather.com/weather/today/l/#Latitude#,#Longitude#] ToolTipType=1 ToolTipTitle=#AlertsTipTitle# ToolTipText=#AlertsTipText# Hidden=1
Si hoc legere scis nimium eruditionis habes. Fac ut vivas.
-
- Posts: 16
- Joined: April 20th, 2020, 8:15 pm
Re: ⭐ Weather.com
Weather.com (and JSBarometer) is suddenly not updating. All the fields that are supposed to auto-populate are empty.
Si hoc legere scis nimium eruditionis habes. Fac ut vivas.
-
- Developer
- Posts: 22851
- Joined: April 19th, 2009, 11:02 pm
- Location: Fort Hunt, Virginia, USA
Re: ⭐ Weather.com
It's fine for me. Try restarting Rainmeter.TheRealDjElite wrote: ↑January 15th, 2021, 7:07 pm Weather.com (and JSBarometer) is suddenly not updating. All the fields that are supposed to auto-populate are empty.
-
- Rainmeter Sage
- Posts: 8442
- Joined: February 27th, 2015, 2:38 pm
- Location: Terra Yincognita
Re: ⭐ Weather.com
TheRealDjElite wrote: ↑January 15th, 2021, 7:07 pm Weather.com (and JSBarometer) is suddenly not updating. All the fields that are supposed to auto-populate are empty.
Didn't test the skin yet, but I agree with jsmorley - it should work. As far as I can tell, it uses some of the same base INC files as his Weather.com skin. As for weather.com itself (the site, the page, etc.) it's working fine, both when grabbing the main page and when grabbing the "separate" JSON.