Re: Saving window maximize state

From: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
To: pgadmin-support(at)postgresql(dot)org
Cc: David Schnur <dnschnur(at)gmail(dot)com>
Subject: Re: Saving window maximize state
Date: 2009-08-31 16:57:03
Message-ID: 200908311857.03846.guillaume@lelarge.info
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

Le mardi 18 août 2009 à 23:23:19, Guillaume Lelarge a écrit :
> Le mardi 18 août 2009 à 20:16:26, David Schnur a écrit :
> > 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
>
> Thanks for your report. It is now logged as a todo:
> http://code.pgadmin.org/trac/ticket/45

Here is a patch to fix this. This is more a new feature than a fix, so it will
be available in 1.11/1.12 release.

I've found also that we don't have minimize and maximize buttons for
properties' dialogs. Should we add them?

--
Guillaume.
http://www.postgresqlfr.org
http://dalibo.com

Attachment Content-Type Size
ticket45_v1.patch text/x-patch 912 bytes

In response to

Responses

Browse pgadmin-support by date

  From Date Subject
Next Message Guillaume Lelarge 2009-09-01 06:26:50 Re: [ADMIN] Background color in query tool
Previous Message Guillaume Lelarge 2009-08-31 12:36:02 Re: 5862-73E9-2F3D problem with sequence