After switching to wxPython 2.9.1.1 (and using Mac OS X with the
Carbon version of wxPython, with Python 2.6) every time I start a
program that uses wx.MediaCtrl, a message box pops up that says:
“Python Information wxQTMediaBackend”. I would greatly prefer this
not happen, but I can't figure out how to stop it.
Oddly, though, I don't see this behavior when running the wxPython
demo, so I guess there's some fix to this, but I can't figure it out.
Below I show an example of a simple stand-alone program that causes
the dialog to appear.
If I recall, 2.9 requires you to call wx.media.PreMediaCtrl() to instantiate it, and then load it afterwards with wx.media.Load()
(I don’t have it installed right now to verify; sorry.)
I think the wx documenatation that shipped with 2.9 has that documented.
I think that's a wxLog message so in the demo it is probably being written to the message pane instead of showing the dialog. In your application you can set a new active log target so the messages will go elsewhere, or you can temporarily suppress the log messages by creating and holding on to an instance of wx.LogNull.
···
On 1/3/11 10:30 AM, Tom wrote:
Dear List,
After switching to wxPython 2.9.1.1 (and using Mac OS X with the
Carbon version of wxPython, with Python 2.6) every time I start a
program that uses wx.MediaCtrl, a message box pops up that says:
�Python Information wxQTMediaBackend�. I would greatly prefer this
not happen, but I can't figure out how to stop it.
Oddly, though, I don't see this behavior when running the wxPython
demo, so I guess there's some fix to this, but I can't figure it out.
Below I show an example of a simple stand-alone program that causes
the dialog to appear.
I think that's a wxLog message so in the demo it is probably being
written to the message pane instead of showing the dialog. In your
application you can set a new active log target so the messages will go
elsewhere, or you can temporarily suppress the log messages by creating
and holding on to an instance of wx.LogNull.
--
Robin Dunn
Software Craftsmanhttp://wxPython.org
Robin -
I used the wx.LogNull as a quick test and it fixed the problem. Many
thanks.