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... ** Also affects: wxwidgets2.8 (Ubuntu) Importance: Undecided Status: New ** Changed in: wxwidgets2.8 (Ubuntu) Status: New => Confirmed ** Bug watch added: trac.wxwidgets.org/ #12778 http://trac.wxwidgets.org/ticket/12778 ** Also affects: wxwidgets via http://trac.wxwidgets.org/ticket/12778 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1007383 Title: Unity does not honour window icons where there is no .desktop file. To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/1007383/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
