coordinates in the designer #2544
Replies: 2 comments 3 replies
-
The decision was made to keep both the code and the designer tool simple. Anything can be changed but I think it is important to ask what the use case is. I can think of some, but I would like to hear it from you. |
Beta Was this translation helpful? Give feedback.
-
Hi, @breiler. Yes, I am for simplicity, too. I also think that consistency should be a priority. The 3D view works fine with negative coordinates, which makes it expected that the designer view will also work. As for the use case, every time you set a Work Coordinate origin inside the machine area, negative coordinates will naturally appear in the designer's view. I do not think it makes the whole thing more complex, it rather makes it simpler and intuitive, IMHO. I was making engraving on a wood round cut. It is natural to set the origin for work coordinates in the middle of the round, for example. I am sure there are many cases when the origin of Work Coordinates is desired to be in the middle of the machine table instead of the left-bottom corner. BTW, the other three corners are also natural to use as origin, but would not work well either in the current designer's view. Moreover, UGS provides an easy way to set the origin of Work Coordinates by clicking the X_0, and Y_0 buttons in the Controller State (DRO) pane. So, if that is so easy and provided, then it is intuitively expected that the designer view is adjusted too, isn't it? As to consistency, I have just opened an issue on a different subject, but it is related to working with coordinates, too: #2545 Thanks a lot for looking into it! |
Beta Was this translation helpful? Give feedback.
-
The designer pane only shows coordinates from zero to whatever the size of the drawing is. When Working Coordinates (which may have negative values) do not coincide with Machine Coordinates (which are always positive), the negative values of the X and Y axes are impossible to display in the designer's view. However, they are still shown correctly in the 3D view, and the code runs as expected in spite of the viewing problem in the designer view.
Is there a reason behind such a design, or is it an overlook in the coding, which can be fixed?
Beta Was this translation helpful? Give feedback.
All reactions