Complete.Org: Mailing Lists: Archives: freeciv-dev: January 2003:
[Freeciv-Dev] Re: (PR#1883) Client is not full aware of game end
Home

[Freeciv-Dev] Re: (PR#1883) Client is not full aware of game end

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: nightmare@xxxxxxxxxx
Cc: freeciv-dev@xxxxxxxxxxx
Subject: [Freeciv-Dev] Re: (PR#1883) Client is not full aware of game end
From: "Jason Short via RT" <rt@xxxxxxxxxxxxxx>
Date: Tue, 7 Jan 2003 13:28:26 -0800
Reply-to: rt@xxxxxxxxxxxxxx

On Tue, 2003-01-07 at 10:51, Raimar Falke via RT wrote:
> On Wed, Jan 01, 2003 at 04:17:51AM -0800, Jason Short via RT wrote:
> > > But even if I have started to make the client aware of the game end if
> > > you consider that you can open a dialog *BEFORE* the game end and have
> > > it still open *AFTER* the game end, then we need a function to popdown
> > > all the dialogs or at least all the possible wrong dialogs when the
> > > status changes, for thi reason PR#533 was related to this one.
> > 
> > popdown_all_game_dialogs is a nice concept, but unreliable.  Only the
> > gtk2 client gets all game dialogs, other GUIs have no means of tracking
> > them all (consider the goto_notify dialogs).  But it seems to me that
> 
> Why not? popdown_all_game_dialogs should do what it name says on all
> GUIs.

It *should*, but not all game dialogs are tracked; it's hard to get them
all.

The GTK2 client queries GTK for a list of open windows and closes
those.  In other clients we just call various functions to close various
windows.  None of these close notify goto dialogs, for instance.

But, none of this is really an issue.  Both of these patches aim to fix
the problem, and both provide other good benefits as well.  So using
both is not a problem.

jason




[Prev in Thread] Current Thread [Next in Thread]