Details
-
Bug
-
Resolution: Unresolved
-
P2: Important
-
None
-
6.5.0 Beta3
-
None
Description
I'm using a draghandler to move a camera in a QtQuick3D scene. As I'm using the Draghandler to modify properties of an item other than its parent I have set its target property to null. The draghandler is the child of an Item which is filled over the View3D scene via anchors.fill: parent
When the signal handler onActiveTranslationChanged is called I am logging the activetranslation via console.log(activeTranslation.length()).
Here are some samples collected when starting a drag a couple of times:
[27.986 ][DBG] 7744.55322265625
[27.997 ][DBG] 18.34433364868164
[28.004 ][DBG] 41.030914306640625
[28.404 ][DBG] 13387.841796875
[28.415 ][DBG] 26.60957908630371
[28.420 ][DBG] 33.050132751464844
[28.433 ][DBG] 54.33715057373047
[28.441 ][DBG] 60.79075241088867
[28.830 ][DBG] 10071.830078125
[28.843 ][DBG] 16.88037109375
[28.850 ][DBG] 22.54119300842285
[28.859 ][DBG] 42.55280303955078
[29.175 ][DBG] 13966.8115234375
[29.190 ][DBG] 40.136722564697266
[29.211 ][DBG] 80.18123626708984
[29.615 ][DBG] 14637.1005859375
[29.628 ][DBG] 28.657140731811523
[30.087 ][DBG] 11021.779296875
[30.101 ][DBG] 15.621131896972656
You can see it contains some hefty large values. This causes my object I am trying to manipulate to shoot off very far and come back intermittently when starting a drag gesture
I am running on a MacBook pro M1, with a logitech M590 mouse as the input device
For screens I am running 2 external 144hz 1080p displays. And the Macbook's screen is turned off (lid closed)