Ed Leafe wrote:

>      I played around some more this afternoon, and managed to see
>      what you were talking about. My earlier tests had everything
>      set up just right, so I never saw this before. I've posted a
>      change today that calls self.scale() upon a successful load;
>      try this out without your modification and see if this fixes
>      it for you. 

        The video frame now appears, but not in the right place.  I think 
the sizer needs to be laid out again.
         
>> I managed to avoid using callAfterInterval by instead binding the 
>> MediaControl's EVT_MEDIA_LOADED event to a method that just runs
>> the form's Sizer.Layout(). 
> 
>      Try to get in the habit of not working at the wx level, as it
>      can get confusing some times. Our goal is to wrap the controls
>      well enough that you shouldn't have to drop to the wx level to
>      do what you need. It would be better to get used to the Dabo
>      events, as we try to include the event information is a much
>      more accessible format. In this case, you should bind the
>      dEvents.MediaLoaded event instead. 

        Ah, I actually looked in dEvents but I guess I missed it.  Is there 
any documentation on the different dEvents?  So far it seems every time 
I want to deal with an event, I have to look inside dEvents.py to see 
what events are available, and even then I can't tell what information 
is available with each event.  Like, if I were writing a MediaControl 
for the first time now, what would be the "right" way to learn that it 
has these events, and how to use them?

Thanks,
-- 
--OKB (not okblacke)
Brendan Barnwell
"Do not follow where the path may lead.  Go, instead, where there is
no path, and leave a trail."
        --author unknown

_______________________________________________
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