Re: how to disable auto-completion - Mailing list pgadmin-support

Hi Michal,

I would suggest that, if you have the time and expertise, to compile pgAdmin 
yourself and disable the hotkey yourself.

I assume that it would take you 1-2 full working days (if you are completely 
new to compiling stuff, probably a lot less), but you'll probably be more 
than happy with the result.

As Dave here suggested, you may state your case with SQL Assistant, since 
you've paid for that product and you are not satisfied. I trust it will take 
them no more than 1-2 hours to provide you with pgAdmin.exe with hotkey 
turned off.

Best regards,
Rade


--------------------------------------------------
From: "Dave Page" <dpage@pgadmin.org>
Sent: Friday, 30 November, 2012 10:40
To: "Michal Kozusznik" <kozusznik.michal@ifortuna.cz>
Cc: <pgadmin-support@postgresql.org>
Subject: Re: [pgadmin-support] how to disable auto-completion

> On Thu, Nov 29, 2012 at 6:46 PM, Michal Kozusznik
> <kozusznik.michal@ifortuna.cz> wrote:
>> On 29.11.2012 13:50, Dave Page wrote:
>>>
>>> What, you mean Ctrl+Space is captured by pgAdmin, even if it doesn't
>>> have focus? It isn't here.
>>>
>>
>> Maybe it's my fault I was not clear enough. I though SQL Assistant is 
>> known
>> app or you will check what is it.
>> This app hook to other app UI replacing/improving functionality. In case 
>> of
>> PgAdmin, after hitting SHIFT+SPACE two popups appears, one over another:
>> from pgAdmin and from SQL Assistant. Actually, the last one has 
>> possibility
>> to change hotkeys, but as I already said, we are accustomed to this since
>> it's most common hotkey for autocomplete/intellisense.
>
> I've never even heard of it, let alone used it. As it hooks in, your
> email makes much more sense than it would if it were a separate app.
>
> However, I still believe that adding an option to disable a single
> hotkey out of many, at the request of one user to enable someone
> else's product to work properly is not something we should do. The SQL
> Assistant website specifically claims that it works with pgAdmin -
> which by the sound of it is inaccurate. It seems to me that it's their
> responsibility to fix - and as it's a paid-for product, you have a
> right to expect it to work as described (in most countries anyway).
>
> Sorry.
>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
>
> -- 
> Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgadmin-support