[PySide] QUiLoader event-related issue/different behaviour

[Félix C. Morency]

Well, I found the problem. I fell in the common pitfall of Python GC.
My objects and event filter were GC'ed after the __init__() method.
Sorry for the trouble.

-F

On Wed, Jul 4, 2012 at 4:32 PM, Félix C. Morency
<felix.morency at gmail.com> wrote:
> Hi,
>
> I came across an unintended behaviour while developing using PySide
> v1.1.1. I created a QMainWindow containing a QHBoxLayout and a
> QMdiArea. To this application, I added two QMdiSubWindow to the
> QMdiArea, containing only an empty frame. I made this application in
> two versions: 1) the GUI is created entirely programmatically [1] and
> 2) the GUI is created with the Qt Designer and loaded at runtime using
> a QUiLoader [2].
>
> The problem is the following: events in the application 2) doesn't
> seems to propagate correctly. In fact, they are never received by the
> corresponding widget.
>
> I installed an event filter to the QFrame to see what's happening. The
> event filter basically just print the type of the event and its
> target. You can see in [1] and [2] the results of the trace after many
> subwindow manipulations (mouse enter, leave, window resize, etc).
>
> Why is this happening? Am I missing something?
> How can we fix this issue, if issue is?
> Is the bug report in [3] related?
>
> [1]: https://gist.github.com/3049256
> [2]: https://gist.github.com/3049311
> [3]: http://bugs.pyside.org/show_bug.cgi?id=533
>
> Regards,
> --
> Félix C. Morency, M.Sc.
> Plateforme d’analyse et de visualisation d’images
> Centre Hospitalier Universitaire de Sherbrooke
> Centre de recherche clinique Étienne-Le Bel
> Local Z5-3031 | 819.346.1110 ext 16634



-- 
--
Félix C. Morency, M.Sc.
Plateforme d’analyse et de visualisation d’images
Centre Hospitalier Universitaire de Sherbrooke
Centre de recherche clinique Étienne-Le Bel
Local Z5-3031 | 819.346.1110 ext 16634