I may be well off the mark and if it is so I apologise up front. The main widget in PyQt and therefore in PySide is the widget that has no parent. Not as easy to see, because when widgets are added to another (parent) widget*, become implicity children of that widget*.
I put a * to the parent widget in order not to further confuse the issue. HTH and apologies if I am talking at cross purposes, OldAl. On Tuesday 16 November 2010 00:45:22 Luke Campagnola wrote: > I see the same problem. I added a bug report here: > http://bugs.openbossa.org/show_bug.cgi?id=471 > > On Sat, Nov 13, 2010 at 17:41, Ryan Kelly <[email protected]> wrote: > > > > > Hi All, > > > > > > Is there any way to determine the thread that is running the main > > event loop? The documentation suggests QApplication.instance().thread() > > but it looks like QObject.thread() is missing in PySide. > > > > I don't need an actual reference to the thread, it would suffice to > > check whether or not I'm running in the main thread (and thus whether I > > can do various operations directly vs posting events). > > > > I'm a wxPython refugee, where we'd use wx.Thread_IsMain() for this > > purpose. Is there a similar function in PySide? > > > > > > Thanks, > > > > Ryan > > > > -- > > Ryan Kelly > > http://www.rfk.id.au | This message is digitally signed. Please visit > > [email protected] | http://www.rfk.id.au/ramblings/gpg/ for details > > > > > > _______________________________________________ > > PySide mailing list > > [email protected] > > http://lists.openbossa.org/listinfo/pyside > > > > > -- Algis Kabaila http://akabaila.pcug.org.au/
_______________________________________________ PySide mailing list [email protected] http://lists.openbossa.org/listinfo/pyside
