Comment 8 for bug 1007383

Peter, the problem you've highlighted with pyQt was related to that toolkit, but also to the fact that you're running the window from a python shell... At that point BAMF identifies that window as a window created by the "python" process (with no argument), so this means that it's python itself. This works well instead, when moving the code you pointed into an external python script.

Gerard, regarding WX widgets this seems to me a problem of the toolkit (see http://trac.wxwidgets.org/ticket/12778), since it doesn't set the proper WM_CLASS for the windows that are loaded using python-wx.

One workaround that can apply to both situations is to ignore some "known loaders" names unless a window icon is set...