Hi guys, I hear ya...it's something I've found a bit hard with GUI programming. The code gets quite large and involved, so boiling it down to a self contained example demonstrating the issue takes some work. But, I agree it's worth doing and the issue very well may be solved during that exercise. In my original post I was simply trying to figure out if this was a known issue or something else completely obvious that I had missed.
I'll see if I can get the issue reproduced in runnable and smaller example. Also, as I said in the original post, I have made sure to call self.setObjectName(__a_unique_name__) on all my QDockWidgets. BZ On Thu, Nov 12, 2009 at 2:17 AM, Hans-Peter Jansen <[email protected]> wrote: > > > Brian, do you expect us to build a runable script from your artefacts? > Please keep in mind, that due to the unlimited permutations of OS, Qt, sip, > and PyQt versions, it's unpossible to estimate the behavior of even the > simplest code fragments in all circumstances (apart from: QWidget.show() > will most likely *not* format your harddisk). > > Therefor, it's a long standing best practice here to provide a self > contained minimum example, the exploits the issue. > > BTW, in my case, 70% of all issues vanish during this exercise, e.g. it's > mostly a "RTFM" or "between keyboard and chair problem"..., another > 20% > by looking into Qt itself. > > I estimate the portion of real sip and/or PyQt issues below 3%. > > Pete > >
_______________________________________________ PyQt mailing list [email protected] http://www.riverbankcomputing.com/mailman/listinfo/pyqt
