[Development] Behaviour change of opacity property in QtQuick 2.0

Alan Alpert alan.alpert at nokia.com
Thu Jul 19 03:29:31 CEST 2012


On Wed, 18 Jul 2012 19:00:01 ext Rafael Brandao wrote:
> I've just figured out this issue on Snowshoe.
> The change is not that simple. Assuming "visible: opacity > 0" will make
> the property rely on this binding, but other entities may change it
> manually what would break that binding, and we really did that. :-(

There's a new enabled property which also prevents mouse input. It also affects 
keyboard focus, but if you aren't using keyboard focus you can bind enabled: 
opacity > 0 and get effectively the same results as before.

--
Alan Alpert



More information about the Development mailing list