Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 228099FBA1E for ; Tue, 13 Mar 2007 13:27:42 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-new, port 10024) with ESMTP id 42356-10 for ; Tue, 13 Mar 2007 13:27:35 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from developer.pgadmin.org (developer.pgadmin.org [63.246.23.140]) by postgresql.org (Postfix) with ESMTP id 6FFCA9FB83F for ; Tue, 13 Mar 2007 13:27:35 -0300 (ADT) Received: from [172.24.32.131] ([62.232.55.118]) (authenticated bits=0) by developer.pgadmin.org (8.13.8/8.13.8) with ESMTP id l2DGR1Uh016359 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 13 Mar 2007 16:27:03 GMT Message-ID: <45F6D0F2.9000609@postgresql.org> Date: Tue, 13 Mar 2007 16:27:30 +0000 From: Dave Page User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: Ezequias Rodrigues da Rocha CC: Pgadmin-Support Subject: Re: Fwd: PgAdmin 1.6.2 crashes when resize the collumn References: <55c095e90703130859n65a6450fkea3df13eb7fc3ef6@mail.gmail.com> <55c095e90703130919v46ef3627mc05b9b75600cf4bb@mail.gmail.com> In-Reply-To: <55c095e90703130919v46ef3627mc05b9b75600cf4bb@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200703/56 X-Sequence-Number: 6771 Ezequias Rodrigues da Rocha wrote: > > > ---------- Forwarded message ---------- > From: *Ezequias Rodrigues da Rocha* > > Date: 13/03/2007 12:59 > Subject: PgAdmin 1.6.2 crashes when resize the collumn > To: PostgreSQL > > > Hi list, > > I had no problem with pgadmin 1.6.2 until I instal PostgreSQL 8.2.3 > > Now when I resize the column in any place the pgadmin crashes. > > Another problem is that when I move the mouse over the table in the sql > dialog the columns are selected. I don't know if it is a problem of the > mouse but the resize of columns are quite problematic. I cannot reproduce either of these issues in 1.6.2 or SVN trunk. Can anyone else? Is there a specific sequence of events that leads to this behaviour? Regards, Dave.