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

Re: pgadmin3

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: <jm(dot)poure(at)freesurf(dot)fr>, <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: pgadmin3
Date: 2003-05-23 08:00:11
Message-ID: 03AF4E498C591348A42FC93DEA9661B83AF0CB@mail.vale-housing.co.uk (view raw or flat)
Thread:
Lists: pgadmin-hackers

> -----Original Message-----
> From: Jean-Michel POURE [mailto:jm(dot)poure(at)freesurf(dot)fr] 
> Sent: 22 May 2003 15:09
> To: pgadmin-hackers(at)postgresql(dot)org
> Subject: [pgadmin-hackers] pgadmin3
> 
> 
> Dear all,
> 
> Just for information, I noticed the following things, while 
> playing around 
> with pgAdmin3:
> 
> - server status does not have a "Cancel" button,

What platform are you on? Is there not a close button supplied by the
Window Manager?

> - query builder cannot lauch due to a segmentation fault,
> 
> Gtk-WARNING **: gtk_menu_attach_to_widget(): menu already attached to 
> GtkMenuItem
> Gtk-CRITICAL **: file gtkwidget.c: line 1388 
> (gtk_widget_destroy): assertion 
> `GTK_IS_WIDGET (widget)' failed.
> Gtk-CRITICAL **: file gtkwidget.c: line 1388 
> (gtk_widget_destroy): assertion 
> `GTK_IS_WIDGET (widget)' failed.
> Gtk-WARNING **: gtk_menu_attach_to_widget(): menu already attached to 
> GtkMenuItem

Is there anything useful in a full debug logfile?

> - it should be possible to enlarge the function windows to 
> display the 
> definition in nearly full-screen,

Agreed. In pga2 we always intended to modify the hbx control to be
detachable from the form into a full text editor.

> - clicking on a view "_RETURN" rule produces an infinite loop.

Looks OK here - are you running current cvs code or a snapshot?

Regards, Dave.

Responses

  • Re: pgadmin3 at 2003-05-23 09:02:03 from Jean-Michel POURE

pgadmin-hackers by date

Next:From: Jean-Michel POUREDate: 2003-05-23 09:02:03
Subject: Re: pgadmin3
Previous:From: Dave PageDate: 2003-05-23 07:41:15
Subject: Re: [pgadmin-support] [ANNOUNCE] pgAdmin Licencing Changes

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