On Thu, 19 Jul 2012 11:06:29 ext Sven Anderson wrote:
> On 19.07.2012 03:29, Alan Alpert wrote:
> > On Wed, 18 Jul 2012 19:00:01 ext Rafael Brandao wrote:
> >
> > There's a new enabled property which also prevents mouse input. It also
> > affects keyboard focus, but if you aren't using keyboard fo
On 19.07.2012 03:29, Alan Alpert wrote:
> On Wed, 18 Jul 2012 19:00:01 ext Rafael Brandao wrote:
>
> 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 th
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 re
On Wed, Jul 18, 2012 at 10:08 PM, Alan Alpert wrote:
> On Wed, 18 Jul 2012 13:47:36 ext Nils Jeisecke wrote:
>> Hi,
>>
>> In QtQuick 1 an element with opacity == 0 is treated as invisible
>> (e.g. it won't see mouse events).
>> This has changed in QtQuick 2.0 which breaks existing code that
>> ass
On Wed, 18 Jul 2012 13:47:36 ext Nils Jeisecke wrote:
> Hi,
>
> In QtQuick 1 an element with opacity == 0 is treated as invisible
> (e.g. it won't see mouse events).
> This has changed in QtQuick 2.0 which breaks existing code that
> assumes that opacity == 0 means !visible.
>
> This example illu
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 Jeis
> 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 complica
On 18.07.2012 13:47, ext Nils Jeisecke wrote:
> Hi,
>
> In QtQuick 1 an element with opacity == 0 is treated as invisible
> (e.g. it won't see mouse events).
> This has changed in QtQuick 2.0 which breaks existing code that
> assumes that opacity == 0 means !visible.
>
> This example illustrates th
Hi,
In QtQuick 1 an element with opacity == 0 is treated as invisible
(e.g. it won't see mouse events).
This has changed in QtQuick 2.0 which breaks existing code that
assumes that opacity == 0 means !visible.
This example illustrates the change. A mouse click will print:
QtQuick 1.1: "CLICKED A"
