|
From: James T. <ja...@fl...> - 2020-09-28 13:51:41
|
> On 28 Sep 2020, at 14:43, Thorsten Renk <tho...@sc...> wrote: > > I *think* Stuart is the person who knows the combined weather GUI (I've grudgingly accepted the need for it...) > > What *probably* is the point here is whether you're driving AW by the METAR string (as in the case of the morning fog) or whether you're calling a native AW scenario (that will be close to the METAR string, but really start the full offline weather engine including weather changes etc.) > > So what /should/ happen for morning fog is that the associated METAR string for the scenario gets parsed and dumped into properties, then AW starts in METAR mode, reads out the properties and starts a METAR-defined weather scenario Ahh okay, so AW can use either method. My concern was if the item was non-functional (in the absence of the local-weather-specific block) : then I’d be aiming to hide the items, or grey them out, when AW is enabled. So long as they are approximately functional (based off METAR), I can remove the warning message, I think. Although, I’ll wait for Stuart to comment to make sure. Kind regards, James |