Crash due to translating first city right after adding about meteo-qt HOT 5 CLOSED

I think that this happened because the unique city in the cities list is not selected by the mouse.
When there are more cities this doesn't occur because there is one focused by default.
I couldn't reproduced if i clicked on the city twice to translate it.

from meteo-qt.

I couldn't reproduced if i clicked on the city twice to translate it.

Sure. The crashes only take place following the steps depicted above. But they are 100% reproducible that way here.

I think that this happened because the unique city in the cities list is not selected by the mouse.

No, unlike I first thought as well this isn't involved. You can see this as follows

1. Set up one or more cities as usual without provoking the crash we're discussing here. Restart meteo-qt.
2. Open dialogue "Cities" from the settings. One of the cities will be marked by some semi-transparent highlighting. Open dialogue "City translation" by clicking button "Translate", leave this dialogue by clicking "Cancel" without taking any action.
3. Back in dialogue "Cities" no city will be selected in any way. Yet clicking "Translate" does not trigger the crash.

Doesn't the CLI output in the GIST linked above suggest the problem is due to some variable not having assigned a value yet under the conditions in question?

from meteo-qt.

I could reproduce it only in this case:

• Add the first city
• Try to translate it just after adding it.
  This change handles the above case.

At all other cases the first city was activated by default by the dialogue.

from meteo-qt.

Yes, the crashes could only be seen under the conditions named above.
But the problem can no longer be seen running d84a7bc here.

from meteo-qt.

Ok, thanks very much for your help

from meteo-qt.