You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment the indicator is using any available provider (mainly US weather office -IWIN-).
Unfortunately this may be less reliable for locations outside the US (especially not major cities).
Switching to OWM may improve things on this aspect and libgweather already supports OWM as a provider but OWM requires an API key for the application to use their API.
At the moment I couldn't find a way to pass the OWM API key value for libgweather to use it and this is blocking the progress to implement this.
I opened an issue/question but it remains unanswered.
If anyone has the answer or can point me in the right direction to pass the OWM API key to libgweather please feel free to share.
Thanks.
The text was updated successfully, but these errors were encountered:
My question above was answered. At the moment there is no way to pass the OWM API key to libgweather at runtime.
They key must be compiled in when building the library so not much I can do at this but to find and alternative to libgweather that can also work with Vala.
Will leave this open for now in case I can find an alternative.
At the moment the indicator is using any available provider (mainly US weather office -IWIN-).
Unfortunately this may be less reliable for locations outside the US (especially not major cities).
Switching to OWM may improve things on this aspect and libgweather already supports OWM as a provider but OWM requires an API key for the application to use their API.
At the moment I couldn't find a way to pass the OWM API key value for libgweather to use it and this is blocking the progress to implement this.
I opened an issue/question but it remains unanswered.
If anyone has the answer or can point me in the right direction to pass the OWM API key to libgweather please feel free to share.
Thanks.
The text was updated successfully, but these errors were encountered: