Why does dragging dynamics not work well?

[uliska]

Dynamic texts do respond to being clicked and dragged, but they don't really work well when being dragged.

I can't see why that is. They must be collected through being a link and having "transform", otherwise there wouldn't be any reaction. But from the code I'd assume that they behave exactly as the other text elements.

[PeterBjuhr]

They are more complex elements. The are drawn as paths in the SVG file and have except the transform attribute also other coordinates which I guess also have to be changed...

[uliska]

I see that in a text element transform has the form transform="translate(22.9264, 5.4842)" while in a path element it is transform="translate(22.9264, 11.0342) scale(0.0040, -0.0040)"

I don't think the other attributes (i.e. the path definition itself) should be the reason.

[PeterBjuhr]

I don't think the other attributes (i.e. the path definition itself) should be the reason.

I think you have a point! But you could argue the same for the scale setting, which would mean that we should be OK by just setting the transform translate.

I'll test some more tomorrow!

[PeterBjuhr]

The scale parameter seems indeed to only affect the size and not the position.

[uliska]

my question would be what difference we get when retrieving the
transform object of a path compared to that of other elements.

[PeterBjuhr]

Yes, and that's what we been discussing. My first thought was that the position was also affected by some other parameter in the element, but I think we can rule that out...

[PeterBjuhr]

Here's another thought and it's also related to #3 (although it doesn't answers the question there):

The paths (in this case dynamics) are comparably harder to drag because the mouse must be over the actual path. (With the texts the mouse could also be over the white areas in the text.) If you zoom in more, it makes it easier and the problems are less.

Initially my implementation for the dragging didn't adjust to the grid until the dragging was finished to avoid problems with mouse position compared to object position. But at first the grid was more spacious when rounding to only one decimal so then it was more important. Then pretty quick the grid got tighter with rounding to two decimals. Next thing was that you changed the functionality so the grid was already active during dragging, i e the positions was continuously rounded. That seemed OK when we only tested with text objects. But when moving on to also other objects which have a smaller "dragging area" (or what you should call it) the mouse seems to fall off, causing dragging problems. I've noticed this before but haven't completely addressed the problem.

[PeterBjuhr]

We're approaching our first milestone. After that I think the next step is to discuss a solution to this.