touch-packages team mailing list archive

[Zsombor Egri <1535480@xxxxxxxxxxxxxxxxxx>]

See comment #2. And let me come with an example Qt screwed up from one
version to the other.

MultiPointTouchArea. The default component was handling only touch
events, not taking care of the Mouse events. In order to handle mouse
event you had to put a MouseArea inside of it, and then one handled the
touch, the other the mouse events. At some point upstream introduced the
mouseEnabled property with a default value of true. From that point the
MouseAreas placed inside the MultiPointTouchAreas were not getting any
mouse events, as the default behaviour of the MultiPointTouchArea
changed. This is not an API break, but a behavioural one.

We are in the same situation. We must introduce the API with backwards
behavioural compatibility, so UI won't look like tiles coming up one
after other just because the icon loading suddenly became asynchronous.
Beside, the property will be exposed, so I do not understand your
opposed to keep backwards behavioural compatibility.

And btw, the Scrollbars dump loads of binding loop warnings with default
asynchronous behaviour...

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1535480

Title:
  Icon image loading is synchronous

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  The Image {} in Icon*.qml is not setting asynchronous to true.

  I would suggest to set it to true so the loading is not blocking the main thread.
  If you don't want to set it to async by default maybe you can add an alias so we can set it externally?

  What do you think?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1535480/+subscriptions