The UltimateListCtrl in my app is currently receiving EVT_CHAR events
only for the arrow keys and the num pad. Anyone have any idea why this
might happen? Is there a reverse WANTS_CHARS style? Using the
inspection tool key ups/downs are working fine..
This started after picking up trunk and perhaps is related to this fix
below, but the wxPython ULC demo correctly receives EVT_CHARs.
http://trac.wxwidgets.org/ticket/11888
http://trac.wxwidgets.org/changeset/64008
That change shifts the focus away from the ULC and to its child self._mainWin, so that is where the EVT_CHAR events are going now.
On 6/16/10 12:35 PM, Mark wrote:
The UltimateListCtrl in my app is currently receiving EVT_CHAR events
only for the arrow keys and the num pad. Anyone have any idea why this
might happen? Is there a reverse WANTS_CHARS style? Using the
inspection tool key ups/downs are working fine..This started after picking up trunk and perhaps is related to this fix
below, but the wxPython ULC demo correctly receives EVT_CHARs.wxTrac has been migrated to GitHub Issues - wxWidgets
wxTrac has been migrated to GitHub Issues - wxWidgets
--
Robin Dunn
Software Craftsman
Unfortunately the EVT_CHARs are not showing up there either and I
believe ULC was propagating them to the parent... As I said the demo
app works fine, its only my app where the EVT_CHARs are not appearing
EXCEPT for the arrow keys. Was hoping this was some odd style or
mistake someone else has seen before..
Using the InspectionTool the ULC child _mainWin is what I'm looking at
when I see the EVT_CHAR appear only for arrow keys.
Mark
On Jun 17, 7:41 am, Robin Dunn <ro...@alldunn.com> wrote:
On 6/16/10 12:35 PM, Mark wrote:
> The UltimateListCtrl in my app is currently receiving EVT_CHAR events
> only for the arrow keys and the num pad. Anyone have any idea why this
> might happen? Is there a reverse WANTS_CHARS style? Using the
> inspection tool key ups/downs are working fine..> This started after picking up trunk and perhaps is related to this fix
> below, but the wxPython ULC demo correctly receives EVT_CHARs.>wxTrac has been migrated to GitHub Issues - wxWidgets
>wxTrac has been migrated to GitHub Issues - wxWidgetsThat change shifts the focus away from the ULC and to its child
self._mainWin, so that is where the EVT_CHAR events are going now.--
Robin Dunn
Software Craftsmanhttp://wxPython.org