On Jan 2, 2010, at 9:52 PM, Paul McNett wrote:
> By the way, this sounds very interesting to me. Ed, why couldn't we think of
> a dApp
> property name, like FilterEvents, that would set up a callback function to
> trap those
> events - I assume they'd be raw wx events at this stage - and raise the
> appropriate
> dabo events?
I see a couple of issues. For one thing, there is not a 1:1
relationship between wx events and Dabo events; part of the whole Dabo event
model is to get around the ridiculous number of wx events and replace them with
just a few sensible Dabo events.
Also, after reading about this functionality, it seems that it is a
huge performance hit in wx, since *every* event has to get the extra processing
of running through the FilterEvents method.
> It would be work but if I'm understanding it, it would be very useful. IIRC,
> we'd be
> able to implement KeyPreview (respond to keyboard events at the form or app
> level
> *before* the active control got the event).
Not only would it be work, but it would be difficult to design this in
a manner that wasn't completely wx-specific.
I'm leaning more toward making it easier to subclass and extend uiApp,
like we do with other contained classes, such as grid columns, tree nodes,
pages, etc. This way a developer who wants to add wx-specific code can do so
much more easily.
-- Ed Leafe
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message:
http://leafe.com/archives/byMID/[email protected]
