Not fixed for 2.4 yet.

Gtk clients: Don't store spy action information in static variables

Unlike the other clients the Gtk clients won't wait until the previous spy
action is complete, follow up questions and all, before the next spy action
dialog is shown.

They used to store information like actor and target in static variables.
Follow up questions would use those variables. The variables would be
overwritten when the next spy action selection dialog was opened. This would
cause orders from follow up questions to be issued to the wrong actor and
against the wrong target.

Changes:

• Use actor and target information sent by the server with the follow up

questions now that the API forwards it.

• Store actor and target information in the GUI widgets using gpointer so

the functions called by the GUI can get it from there.

See bug #21636

(Browse SVN revision 26204)

(Versions for 2.4 and 2.5 will come later)

2.4.3 is imminent and there's no patch (it's probably too late to rush one in), so removing 2.4.3 target.

Is there any connection to another unit type with action popups, caravans.

In any case I'd like to see diplomat & caravan actions brought together, so that long standing limitation that same unit cannot sensibly have both diplomat and caravan flag would be lifted (problem currently being that for such a unit only one action popup would be presented, so there's no way to make actions of the other kind)
Do you have any plans of this? I also assume that it would mean enabling caravan actions via action enablers.

Some diplomat actions require two steps of input. The first step selects the action, the second give details like what improvement to sabotage. The Gtk client moves on to the next diplomat waiting for user input as soon as an action is chosen. Since a lot of data is shared this confuses the second diplomat.