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

Re: Possible frmMain.tv_NodeClick bug

From: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
To: "'jm(dot)poure(at)freesurf(dot)fr'" <jm(dot)poure(at)freesurf(dot)fr>
Cc: pgadmin-hackers(at)postgresql(dot)org
Subject: Re: Possible frmMain.tv_NodeClick bug
Date: 2002-03-04 19:48:23
Message-ID: FED2B709E3270E4B903EB0175A49BCB1047664@dogbert.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: 04 March 2002 18:26
> To: Dave Page
> Cc: pgadmin-hackers(at)postgresql(dot)org
> Subject: [pgadmin-hackers] Possible frmMain.tv_NodeClick bug
> 
> 
> Hi Dave,
> 
> I noticed that "frmMain.tv_NodeClick frmMain.tv.SelectedItem" 
> was used 
> several times to simulate a node click.
> 
> When opening several objects simultaneously, this might 
> generate bugs. What 
> do you think?

No, I don't think that will cause a problem as it will always redisplay
whatever is currently selected in the treeview, not the opened object.

I am considering another related fix though - the code that searches for the
nodes to add, drop or update is no longer required *I think*. Originally,
objects in pgSchema had no knowledge of their parents in the hierarchy, so
there was no easy way to locate the precise node in the tree. Nowadays, each
object has a Database, and possibly Table property so we should be able to
precisely figure out the correct node just by checking the relevant
properties.

Regards, Dave.

pgadmin-hackers by date

Next:From: Dave PageDate: 2002-03-04 20:33:59
Subject: Re: Pseudo alter triggers
Previous:From: Jean-Michel POUREDate: 2002-03-04 18:26:01
Subject: Possible frmMain.tv_NodeClick bug

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