On 8/21/13 7:14 PM, "Alan Alpert" <4163654...@gmail.com> wrote:
>On Wed, Aug 21, 2013 at 8:31 AM, Josh Faust
>wrote:
>>
>> On Tue, Aug 20, 2013 at 12:44 AM, Nils Jeisecke
>> wrote:
>>>
>>> On Tue, Aug 20, 2013 at 6:15 AM, Josh Faust
>>> wrote:
>>> >I'm curious what the reasoning behind this is.
On Wed, Aug 21, 2013 at 8:31 AM, Josh Faust wrote:
>
> On Tue, Aug 20, 2013 at 12:44 AM, Nils Jeisecke
> wrote:
>>
>> On Tue, Aug 20, 2013 at 6:15 AM, Josh Faust
>> wrote:
>> >I'm curious what the reasoning behind this is. Is it just a performance
>> > optimization?
>> I think so. Currently scen
On Tue, Aug 20, 2013 at 12:44 AM, Nils Jeisecke wrote:
> On Tue, Aug 20, 2013 at 6:15 AM, Josh Faust
> wrote:
> >I'm curious what the reasoning behind this is. Is it just a performance
> optimization?
> I think so. Currently scene items don't get a notification if their
> absolute positioning cha
On Tue, Aug 20, 2013 at 6:15 AM, Josh Faust wrote:
>I'm curious what the reasoning behind this is. Is it just a performance
>optimization?
I think so. Currently scene items don't get a notification if their
absolute positioning changes while the relative position to the parent
does not.
See http:
>From the MouseArea docs:
Warning: This property is not updated if the area moves under the mouse:
containsMouse will not change
I'm curious what the reasoning behind this is. Is it just a performance
optimization?
I ask as it makes a number of things not work properly when:
* The window resize
