[Development] Behaviour change of opacity property in QtQuick 2.0

[Rafael Brandao]

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. :-(

On Wed, Jul 18, 2012 at 12:59 PM, Nils Jeisecke <njeisecke at saltation.de>wrote:

> > Apparently, it was intentional: QTBUG-19193, and commit
> > 9bf96613c1be7d4df7132a9c3c9ac1a8740f698f. It would be nice to know what
> > the arguments for changing the behaviour were...
>
> Ok, thanks. I should have checked the git log. Sorry.
>
> However this change makes QtQuick porting even more complicated
> because it can be quite hard to figure out why a mousearea that is
> below some invisible popup (visible but opacity==0) no longer reacts
> to clicks but to hover events...
>
> Nils
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>



-- 
Rafael Brandao @ INdT
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20120718/87cd3245/attachment.html>