FYI, I am on 2.10.3, and behavior is exactly the same as denoted in this thread, so there has been no change for a long while.
I guess I am wondering why this is suddenly a problem. If touch screens are only recently being introduced, my experience with them is that you do not have to 'go get' the cursor; if one touches outside the cart identifier box, the cursor will jump to where the finger-press is. Just do not touch inside the cart box first if not intending to duplicate it. --Chuck On Tu, 31 Dec 2019 14:56:04 -0500 Fred Gleason <[email protected]> wrote: > On Dec 31, 2019, at 03:03, Mircea Paun <[email protected]> wrote: > > So ...I must accept that the second result of a drag & drop is > > that: > > If you use touchscreen you have more than 50% chance to duplicate > > cart rathet than setup a transition of next cart to stop or seg or > > set a timed event. > > > > So, a cool feature will be desabled... > > Perhaps not... > > I?ve just committed a change to Git ?master? that makes dragging an > event from the Button Log a bit less ?hair-trigger?. Specifically, > after pressing the mouse button (or touching the screen), the cursor > must be moved at least 20 pixels before a drag event is generated. > This will hopefully make the behavior with a touch screen a bit more > predictable. > > Please test! > > Cheers! > > > |-------------------------------------------------------------------| > | Frederick F. Gleason, Jr. | Chief Developer | > | | Paravel Systems | > |-------------------------------------------------------------------| > | A room without books is like a body without a soul. | > | | > | -- Cicero | > |-------------------------------------------------------------------| > > _______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
