From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
Cc: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | Re: Patch to fix Debian Bug #451038 |
Date: | 2009-07-24 12:38:03 |
Message-ID: | 937d27e10907240538w73432b35h8a8ac8dd2ec7053b@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
On Fri, Jul 24, 2009 at 1:23 PM, Guillaume
Lelarge<guillaume(at)lelarge(dot)info> wrote:
> Le vendredi 24 juillet 2009 à 12:20:28, Dave Page a écrit :
>> On Fri, Jul 24, 2009 at 11:14 AM, Guillaume
>>
>> Lelarge<guillaume(at)lelarge(dot)info> wrote:
>> > I've tried to check different parameters but failed. The only way I found
>> > (and the last I tried) is using the tab count. The last because I don't
>> > like it either. One other way is to loop though all the tabs and check if
>> > we have an "SQL" tab. It should protect us enough of the issue you're
>> > talking about?
>>
>> Can we set a flag at the point where we create the tabset, and check that
>> later?
>>
>
> Another way to do it is to check the object before executing the Enable
> method. See patch attached.
Seems clean, safe and effective.
:-)
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | svn | 2009-07-24 13:38:02 | SVN Commit by guillaume: r7982 - in branches/REL-1_10_0_PATCHES/pgadmin3: . pgadmin/agent pgadmin/dlg |
Previous Message | Guillaume Lelarge | 2009-07-24 12:23:06 | Re: Patch to fix Debian Bug #451038 |