Re: Some wx behavior questions - Mailing list pgadmin-hackers

From Dave Page
Subject Re: Some wx behavior questions
Date
Msg-id 03AF4E498C591348A42FC93DEA9661B8720059@mail.vale-housing.co.uk
Whole thread Raw
In response to Some wx behavior questions  (John McCawley <jmccawley@worleyco.com>)
Responses Another wx behavior question  (John McCawley <jmccawley@worleyco.com>)
List pgadmin-hackers

> -----Original Message-----
> From: John McCawley [mailto:jmccawley@worleyco.com]
> Sent: 21 November 2003 15:37
> To: pgadmin-hackers@postgresql.org
> Subject: [pgadmin-hackers] Some wx behavior questions
>
> If you guys would rather I direct my wx related questions to
> the wxWindows project let me know, but I would prefer to be
> active here since my project's purpose is closely related to pgAdmin.

Hi John,

Please feel free to ask your questions here, I can't speak for everyone,
but certainly the main dev team will always help out where possible.
That said, the wx guys do know more about their code than we do, so you
may benefit more from asking them (though the one and only time I tried
this the silent response was deafening :-( ).

As for this particular problem, a few thoughts spring to mind (haven't
investigated the feasibility though):

- Set an access key on your Cancel button/Exit menu option

- wxCommandEvents are recursively applied to the parent windows event
handler. If you derive your own text control, can you catch the keypress
and raise your own wxCommandEvent?

- Derive your own controls and override the OnChar event handler (as
above) but this time call a public exit() method in the parent
frame/dialogue.

I would add that I would be hesitant to put code based on the second two
ideas in the pgAdmin tree as it would likely be a lot of extra classes
that implement a 'nicety' not in the rest of the code.

Regards, Dave.

pgadmin-hackers by date:

Previous
From: Andreas Pflug
Date:
Subject: Re: Some wx behavior questions
Next
From: Devrim GUNDUZ
Date:
Subject: Build errors on Fedora, latest snapshot