Dave Page a écrit :
On Mon, Jun 16, 2008 at 11:07 PM, Guillaume Lelarge
<[EMAIL PROTECTED]> wrote:
OK, this works on my local branch but I still have one issue with it: if the
user change the name of a newly created object in the SQL text field, the
treeview will display the name available in the name field, not the real one
available in the SQL text field.
The only way I can think to handle that is to refresh the parent
collection, not just the object being modified.
That's also the way I wanted to handle this. But we get back to the
refresh issue. I will need to fix this one.
That can be
potentially dangerous if the user has another property dialogue for a
sibling object open though (actually that's an issue now iirc - this
would just make it far more likely to occur).
What kind of issue are you talking about? can you give me an example?
--
Guillaume.
http://www.postgresqlfr.org
http://dalibo.com
--
Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-hackers
