On Thu, Jun 2, 2011 at 11:29 AM, Dave Page <dpage(at)pgadmin(dot)org> wrote:
> On Thu, Jun 2, 2011 at 9:46 AM, Kieran McCusker
> <kieran(dot)mccusker(at)kwest(dot)info> wrote:
>> If we cannot go back to lazy loading these tabs would it be possible to
>> disable or hide these tabs and the corresponding querys in File ->
>> Options (similar to the browser tab or maybe a general "simple mode"
>> type idea).
> I'll look into it.
I figured out a way of detecting if a tab is visible, regardless of
whether it is currently selected, so with that info we can ensure we
only load the listviews that are currently visible (or are about to
become visible, if the tabset selection is changing). I also realised
that we were loading the three most expensive tabs twice every time
the selected object was changed(!), so even if all tabs are visible it
should be twice as fast as it was now.
I also cleaned up the code that does this, as it had become somewhat
spaghetti-like, and had duplication in a number of code paths.
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
In response to
pgadmin-support by date
|Next:||From: Ben Carbery||Date: 2011-06-04 01:49:17|
|Subject: Re: pg_listener table errors with slony|
|Previous:||From: Belbin, Peter||Date: 2011-06-02 18:37:22|
|Subject: Re: Pgadmin III loses connection with remote
database and then hangs for a long time.|