X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X_CMAE_Category: , , X-CNFS-Analysis: v=2.2 cv=APCo28jM c=1 sm=1 tr=0 a=uZQz0Left1ab2btRV2iqXg==:117 a=uZQz0Left1ab2btRV2iqXg==:17 a=N659UExz7-8A:10 a=jI1DAkUlAAAA:8 a=QXkFsr7TyJOOGFrbP7cA:9 a=R8JmxLazyK91r_Uf:21 a=6ln1zHy-eIgRsIMo:21 a=1URV6StUMUUA:10 a=6-w5dWVApBJDS3X50Ur4:22 X-CM-Score: 0 X-Scanned-by: Cloudmark Authority Engine X-Authed-Username: TGFycnlAZ2x1ZWxvZ2l4LmNvbQ== Subject: Re: [geda-user] RFC: gtk-hid window size save/restore To: geda-user AT delorie DOT com References: From: Larry Martin Message-ID: Date: Tue, 14 Jun 2016 14:31:36 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit 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 Precedence: bulk > remember window geometry and tries to restore it to the last known state Visual Studio has a mechanism that works well for me and my team (when I have one). GUI settings are kept in a .suo file alongside the .sln. I do not check in the .suo file. So everyone gets the important setups in the .sln file, but everyone is also free to make their own look&feel decisions, on a per-project basis, in their own .suo files. I would suggest this kind of split to anyone considering this kind of question in a GUI for technical work. Neither file is hidden btw. I can also argue against any attempt to save window geometry. I work on a laptop. At home I run 3 screens - native, HDMI and SVGA. On travel I have just the one. Some of my most frustrating GUI interactions are on travel when a window instantiates on a screen that is not currently connected. fwiw, thanks for all you do. Larry On 6/14/2016 1:58 AM, gedau AT igor2 DOT repo DOT hu wrote: > Hi all! > > I've arrived at the gtk hid's "window width/height save/restore" code in > my conf-rewrite in pcb-rnd. Long story short: the gtk hid tries to > remember window geometry and tries to restore it to the last known state > (?) when pcb is started. > > Thinking it over, I am not sure this is a good idea (while I totally see > why many users probably want it). > > I am interested in your input, as an user of GUI apps in general (I > don't think this is pcb-specific) about how this is best done. > Conceptually the question is, assuming pcb-rnd needs to save/restore > window sizes, whose property window sizes is? The program's? The user's? > The desing's? The session's? This gets tricky especially in corner cases > like laptops with variable screen sizes (large external screen when > docked and small screen on the road). > > Please comment on the following options, or add extra options if you see > any: > > 1. Do not try to save window geometry, let the window manager do its > job. This is how I do it: my wm runs an awk script that regex-matches > pcb windows and arranges the on the fly, overriding whatever pcb says. > PCB windows are automatically arranged in the way I like them, no matter > how big my screen is. This probably won't work for most users because > they use less capable window managers and/or spend less time configuring > it. > > 2. Save it as an user configuration (~/.pcb-rnd/); > this is good as long as you are running only one instance of pcb. When > you start running two in parallel, and chose different window sizes, > they will overwrite eachother's settings so it's random which one wins > (e.g. the one you closed last will overwrite window geometry last). I > think this is how the gtk hid does it these days, but I am not 100% sure. > > 3. Save it as a per-design configuration; it's much less likely that the > same user on the same system opens the same design twice and if he does, > his save operations will fight anyway; however, editing the same design > on multiple screens (or multiple systems, by multiple users!) makes it > pretty wrong to save this setting in the design. Having some local > settings stored in an unversioned config file next to the .pcb file > solves some of the problems, but not all (e.g. same user, same system, > screen size changes) > > 4. make it an "explicit save" thing so it doesn't try to save it > automatically, it makes a snapshot only when you explicitly click a > button. Window geometry is saved in ~/.pcb-rnd/ (user config). So if you > know you are going to use a given screen size for the next period of > time, you rearrange your windows, save the arrangement then if you start > new pcb instances they start with this saved setting. > > NOTE: I am not proposing any change to pcb or gschem or geda/gaf. > > Regards, > > Igor2 > -- Larry Martin www.GlueLogix.com RFID for Label, Card and Plastics Companies desk/cell USA 919.342.0201