From: | Dave Page <dpage(at)postgresql(dot)org> |
---|---|
To: | Erwin Brandstetter <brandstetter(at)falter(dot)at> |
Cc: | pgadmin-support(at)postgresql(dot)org |
Subject: | Re: pgadmin 1.8.0 beta3 bug |
Date: | 2007-08-29 10:43:03 |
Message-ID: | 46D54DB7.4070201@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
Erwin Brandstetter wrote:
> dpage(at)postgresql(dot)org wrote:
>> Erwin Brandstetter wrote:
>>
>>> If any change via properties dialog would collapse the whole table
>>> subtree that would be a change for the worse IMO. Then I'd rather have
>>> the status quo ante.
>>> Is there no way to just refresh the SQL pane?
>>>
>>
>> Not really - it's generated from all the other bits of data. I updated
>> the .exe at http://developer.pgadmin.org/~dpage/pgadmin3.zip; try it out
>> and see what you think.
>>
>
> Thanks, got it and tested it.
> Having the whole table subtree collapse with any adjustment kills the
> workflow. If, for instance, I want to add /change comments for a dozen
> fields of a table this quickly becomes a pain.
OK, I figured out how to hierarchically retain the expanded/collapsed
state of the child nodes during refresh - turned out to be *much* easier
that I thought it would be.
I've updated the .exe again - please let me know what you think.
/D
From | Date | Subject | |
---|---|---|---|
Next Message | Raymond O'Donnell | 2007-08-29 10:58:53 | Re: pgadmin 1.8.0 beta3 bug |
Previous Message | Mester József | 2007-08-29 09:46:37 | Install problem on debian etch |