-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Polyline origin position is not quite intuitive #882
Comments
I think ideally, the origin would be separately visualized and could be explicitly edited. This could be useful because it may for example affect the origin of rotation when the polygon is used as a physics body. |
That would solve it! It would fit every need i can think of. |
For the last dev build (I downloaded it there https://ci.appveyor.com/project/bjorn/tiled/build/job/sr7rg819u8ue9bii/artifacts) it works with a little bug. The origin point is drawed, ok, but when I edit the poly's origin I am expecting: |
It's not the origin point that is visualized, hence this issue is still open. The larger dot is actually just the first one. This was done in order to be able to tell the difference between the start and the end of a polyline for example (#601). I plan to try adding an origin marker, which will also indicate object rotation, as suggested on the forum. |
Whenever a polyline is created the origin is set to the first coordenates you clicked, and if you edit this first vertex and change the overall size of the polyline this origin position does not change. So it´s easy to lose the graphic representation of what the polyline (x,y) position means (specially if you use the move tool, because that updates the polyline position).
Maybe is more intuitive to define the position of a polyline by the top left corner of the rectangle that surrounds it, and update if you edit the vertexes. Since the first vertex coordenates are always (0,0), you could parse it the same way, it´s just easier to understand what the polyline (x,y) position really is.
The same applies to the polygon tool.
The text was updated successfully, but these errors were encountered: