Ah, I'm used to documentation that documents the entire class :-) That 
will be where the confusion came from.

Would it be possible to, instead of just silently omitting the inherited 
items, to instead add a section tot he the end of each classes 
documentation that says some thing like the following items are 
inherited from wx.<whatever> and then just list the names with no other 
details? It's rather confusing to see code using a Dabo class but 
referencing items that are not listed in the Dabo documentation.

Actually, now I'm even more confused. I went to the wxPython web site to 
look at the docs for wxApp and their documentation lists FilterEvent, 
but it makes no mention of SetCallFilterEvent.

Am I right in guessing that this is also a wxApp method and that their 
documentation is missing it for some reason?

Ian Simcock.




Paul McNett wrote:
> On 2/6/12 5:01 PM, Ian Simcock wrote:
>> I'm still a bit confused. The code snippet Jacek posted sets the
>> UIAppClass to the UIApplication class which is defines in the snippet as
>> a subclass of "dabo.ui.uiApp". When I look at the API docs at
>> "http://paul.dabodev.com/doc/api/dabodoc/dabo.ui.uiwx.uiApp.uiApp.html";
>> I see not mention of FilterEvents or SetCallFilterEvents.
>
> FilterEvents and SetCallFilterEvents are members of wx.App, inherited by 
> dabo.ui.uiApp.
>
>> How do they get there? Are they being added to the Application object in
>> the background by the UI system because it sees it's WX, or is there
>> some inheritance I'm not seeing or what.
>
> It gets multiply-inherited from wx.App in line 111 of 
> dabo/dabo/ui/uiwx/uiApp.py:
>
> 111 class uiApp(dObject, wx.App):
>
>
>> Sorry if it's a silly question. I've only ever written a couple of small
>> python programs, and none of the using Dabo yet, so I could be easily
>> missing something.
>
> Not a problem at all. Dabo has a lot of redirections and layers that makes it 
> pretty
> confusing to understand. While we could have done so, we didn't want to pull 
> in the
> wx layer into our auto-generated api docs because it would have added way too 
> much
> noise. If FilterEvents() is useful, what we should do is make a dabo wrapper 
> for it
> (and document that).
>
> Paul
>
> _______________________________________________
> 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]
>
_______________________________________________
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]

Reply via email to