Skip site navigation (1) Skip section navigation (2)

[pgAdmin III] #45: Saving window maximize state

From: "pgAdmin Trac" <trac(at)code(dot)pgadmin(dot)org>
Cc: pgadmin-hackers(at)postgresql(dot)org
Subject: [pgAdmin III] #45: Saving window maximize state
Date: 2009-08-18 21:21:40
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgadmin-hackers
#45: Saving window maximize state
 Reporter:  David Schnur  |       Owner:  dpage  
     Type:  bug           |      Status:  new    
 Priority:  minor         |   Milestone:  1.10.1 
Component:  pgadmin       |     Version:  1.8    
 Keywords:                |    Platform:  windows
 Almost all Windows applications remember the maximize state of their
 windows the next time they start up.  I've noticed that this is not true
 for pgAdmin; by default it always starts up non-maximized.  Changing the
 shortcut's properties to force maximization works for the main window, but
 new query windows are still non-maximized.

 This is a minor issue, but saving the maximize state is a very widely-
 accepted convention.  Windows users are accustomed to closing a maximized
 window by moving the mouse to the upper-right corner of the screen.  A
 window, i.e. a new query window, that always starts up non-maximized can
 be irritating, because the usual gesture to close it ends up closing the
 application behind it instead.

 Using version 1.10.0 (also present in 1.8.4) on Windows XP Pro SP3

Ticket URL: <>
pgAdmin III <>
pgAdmin III


pgadmin-hackers by date

Next:From: pgAdmin TracDate: 2009-08-19 07:53:37
Subject: [pgAdmin III] #46: "Use Replication" label/field bug in Column Create/Edit Dialog
Previous:From: pgAdmin TracDate: 2009-08-17 10:22:35
Subject: [pgAdmin III] #44: Ensure frmEditGrid survives a drop/create of the underlying relation

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group