From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Euler Taveira de Oliveira <euler(at)timbira(dot)com> |
Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>, Hiroshi Saito <z-saito(at)guitar(dot)ocn(dot)ne(dot)jp> |
Subject: | Re: unpleasant characters |
Date: | 2009-12-14 16:27:17 |
Message-ID: | 937d27e10912140827v4de7bb5bj32536ec0cde10a42@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
On Mon, Dec 14, 2009 at 2:02 PM, Euler Taveira de Oliveira
<euler(at)timbira(dot)com> wrote:
> Dave Page escreveu:
>> Do you know if this will have any unpleasant side-effects in Japan or
>> other regions with what we would consider to be unusual keyboard
>> layouts?
>>
>>
> As I said, I don't know if we'll have problems with it; but if they map Fx key
> to some character, they have trouble using our shortcuts anyway. Could Hiroshi
> or someone else confirm this? If we have problems, I'm afraid the only path is
> coding OnChar() (which would be a pain in the neck because we'll have to
> maintain code that IMHO is WX responsibility).
>
> I noticed that even if we don't event.Skip() on OnKeyDown() event (the patch)
> the shortcut is executed (for example F5) maybe because it is caught by
> OnKeyUp(), another key event, or another object? I don't know how events are
> handled in WX but somehow OnKeyDown() are processed _before_ OnChar() so the
> character are not printed. Also, it didn't prevent another object (wxMenu) to
> capture that event too.
>
> Did you reproduce the problem?
Nope - cannot reproduce any problem here, but then my Windows machine
is running in vmware fusion which may not be helping matters.
Anyone else?
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2009-12-14 16:27:57 | Re: unpleasant characters |
Previous Message | Dave Page | 2009-12-14 16:25:53 | Re: pgAdmin3 icon |