[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pykde
Subject:    Re: [PyQt] QML non-NOTIFYABLE property warning on Person example.
From:       Phil Thompson <phil () riverbankcomputing ! com>
Date:       2014-10-24 21:33:25
Message-ID: 8b984ac1cd158b3664b00d4072a7ba10 () riverbankcomputing ! com
[Download RAW message or body]

On 24/10/2014 10:13 pm, bootch@nc.rr.com wrote:
> I get some such warning from QML engine when I do something like:
> "MenuItem { enabled: person.shoe " where Person is defined on the
> Python side and registered per the example in the PyQt documentation.
> (I want a menu item enabled according to the value of the shoe
> property, supposing shoe was bool.) Is that something I can fix using
> the notify=signal parameter to pyqtProperty?  The PyQt documentation
> says "notify – the optional unbound notify signal. It is ignored by
> Python"  I interpret that to mean that Python doesn't care, but that
> it will have an effect on Qt and QML?  No big deal,  easy enough to
> test it, or work around.  The inner workings are just mysterious to
> me, QML will automagically connect that signal from the instance of
> person to some slot on the instance of menu item?

I think that's the theory.

Phil
_______________________________________________
PyQt mailing list    PyQt@riverbankcomputing.com
http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic