GNOME Bugzilla – Bug 591516
Need some more GWeatherLocation API
Last modified: 2009-08-12 09:13:20 UTC
The current clock cannot remember a custom name that has been set by a user for a location. This is because of some limitation of the GWeatherLocation API. I'll attach a patch to fix this, and the clock patch to show how it's used (and because bugzilla is a good backup ;-))
Created attachment 140511 [details] [review] [libgweather] Add gweather_location_entry_has_custom_name() Also make gweather_location_entry_set_city() return a boolean to know if it's successful.
Created attachment 140512 [details] [review] [clock] Make it possible to change the name of a location For this, we need to make a difference between a city of a location, and the name that is used for it. We save both in gconf (and we gracefully handle migration from old configurations, of course).
Sure. Although to the extent I've thought about GWeatherLocationEntry at all since 2.24 went out, it's been in the context of throwing it out and replacing it with something that queries geonames.org...
I renamed the API to gweather_location_entry_has_custom_text() (which is slightly less bad but still not a good name...) and committed everything. FWIW, I think it makes sense to query geonames.org, but I'm unsure we should completely ditch what we have now -- it's a good "backup" for offline use.