Ideal way to store coordinates in iModel for leaders in TextAnnotation #8365
Replies: 1 comment
-
tl;dr I'm leaning toward local coordinates My opinion. Storing in world coordinates would be more convenient for the typical user interaction where the user wants to adjust the text location but preserve the leader target. However, local coordinates would be more convenient for the case where we want to relocate an entire drawing or part of a drawing. Which ever way we choose to store the points, one of the operations requires custom logic. I'm thinking that the user interaction is more likely to be accomplished by a custom tool designed for the purpose while the wholesale relocation is more likely to be done by generic code that deals with many elements. Assuming that's true, I think it will be easier to do the special logic in the user interaction. Therefore I am leaning toward storing in local coordinates. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
For context : #7830
Merged PR: #8278
I wanted to get some opinions on the information stored for leaders in the Text Annotation.
Currently the data stored looks like this converted to json.
As of now, the startPoint and intermediatePoints are stored in local coordinates i.e. w.r.t the text placement.
When there is a move operation done on the text label, we do not want the startPoint of leader to move w.r.t to the text.
So for the above scenario to work well, we could have the coordinates stored in drawing coordinates instead of local(w.r.t text placement), is that a good approach?
Beta Was this translation helpful? Give feedback.
All reactions