Thanks for the response.
Well, the issues are basically negative visual effects. We use drag and
drop intensively in the application and the user loses agility when
dragging elements. Mainly:
- Before dragging an element both from the tree and from the table, you
must click/tap on it to get it selected and highlighted. If not, you
don't really know what you are dragging (I haven't tried to select the
elements on the drag event yet, and thus I don't know if it could work).
- Selecting and dragging multiple elements is even worse. In the table,
having some elements selected you really only drag the element you put
the mouse over when starting the drag. Again we still haven't tried to
change how our code deals with events and selected elements, but in Qx
3.5 it worked like a charm.
Sadly, I have had to switch back to 3.5 because we are in a bit of hurry
right now and I am not able to do tests right now, perhaps tomorrow or
next week...
On 10/07/14 08:09, Martin Wittemann wrote:
Hey,
We've just migrated a 3.5 application to Qooxdoo 4.0 and we've found
a behavior change in selections that affects the way interaction
occurs in that application.
In 3.5, both in trees and tables (and everywhere I suppose), the
selection of the item is done in the MouseDown event while in 4.0 is
done when the Mouse button is released (MouseUp / PointerUp or Click
/ Tap). I've seen that handleMouseDown() and handleMouseUp() methods
in the manager class have been replaced by a single handleTap()
method, but I still do not find the way to get it working like it did
in 3.5 (I got it partially, but then multi-selections got broken).
PS: I've applied the patch (bug #8434), that was the only related bug
I could find.
You can just view what I am talking about in the showcase:
_
__Qooxdoo 3.5.1_
http://demo.qooxdoo.org/3.5.1/showcase/#Table
http://demo.qooxdoo.org/3.5.1/showcase/#Tree
_
__Qooxdoo 4.0_
http://demo.qooxdoo.org/current/showcase/#Table
http://demo.qooxdoo.org/current/showcase/#Tree
That behavior change was necessary due to the touch support. Scrolling
on a touch device starts with a touch on the item followed by a swipe.
If the widgets change the selection on the first interaction e.g.
mousedown / pointerdown the selection would also change on a touch
scroll which is an unexpected behavior. So this change was necessary
and on intension. :)
Do you still having problems updating your code? If so, what are the
issues?
Regards,
Martin
------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
