X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
Date:	Wed, 15 Jun 2016 14:35:27 +0200 (CEST)
From:	Roland Lutz <rlutz AT hedmen DOT org>
To:	geda-user AT delorie DOT com
Subject:	Re: [geda-user] RFC: gtk-hid window size save/restore
In-Reply-To:	<ee06b627-a697-740d-036a-010162755722@GlueLogix.com>
Message-ID:	<alpine.DEB.2.11.1606151417200.1470@nimbus>
References:	<alpine DOT DEB DOT 2 DOT 00 DOT 1606140744350 DOT 7286 AT igor2priv> <ee06b627-a697-740d-036a-010162755722 AT GlueLogix DOT com>
User-Agent:	Alpine 2.11 (DEB 23 2013-08-11)
MIME-Version:	1.0
Reply-To:	geda-user AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	geda-user AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Tue, 14 Jun 2016, Larry Martin wrote:
> Some of my most frustrating GUI interactions are on travel when a window 
> instantiates on a screen that is not currently connected.

This obviously shouldn't happen, just like mapping a window outside the 
visible area on a screen (e.g. after changing the resolution or connecting 
a different device).

However, I think remembering the screen on which a window was mapped is, 
in general, the right thing to do.  I usually have the main window on one 
screen and auxiliary windows on another screen.  If an application 
remembers the window size but maps each window to the same screen, 
everything ends up garbled together.

In addition, I think whether a window is mapped or not should be 
considered part of the window geometry.  If, for example, the user 
arranges the library, netlist, and message log windows in a column next to 
the main window, all three windows should be visible and arranged the 
right way when PCB is started for the next time.

- Raw text -