Happy New Year to everyone. 2020 is going to be a great year.
Sorry for the 2 months of no releases. Life and major changes in the backend slowed the release.
The only noticeable change is how you add/remove data via “Select Data” in the top right menu. This is much faster and easier.
So beta testers, with the major changes in the backend there will be bugs so please keep an eye out for them critters.
@duane absolutely love the new update so cool as Always Keep up the Great Work
Great update!
One critter detected: app or widget range change requires some jiggery.
From here, Select Data works (though I might like to be able to provide a display order…) and the radar display is much improved.
Been stable so far.
Thanks!
The display order can be changed by a long hold.
So it does! thank you!
Sorry I forgot to mention the long-press to reorder.
BTW, @Alex, I don’t think the range bug is part of this update since I didn’t touch that part of the code. Must be another bug.
Cheers, Duane.
Arome has lost it’s validity boundary lines. Normally there is quite a distinct demarcation line between Arome and GFS. Now, there is none.
Which poses the question, is the map really Arome?
Arpege, Hirlam and KNMI boundary lines are intact.
Thanks @Alex,
Indeed, Arome is broken. Arome is special, there are actually two domains, a larger one with lower resolution and a smaller one with higher resolution - I merge them together into one data source. This is the special case that is making it break. I’ll look into it.
I’ll release the next beta release (in the next hours) and then look into the Arome issue for the following beta release.
Cheers, Duane.
The snow icon is showing on GFS maps although it is not being supported.
Hi @Alex
Yes, this is a pre-3.222 bug. It’s actually a bug on the server where it’s not processing the GFS snow data properly. It’s high on my to-do list.
Cheers, Duane.