Community

AutoLISP: MText: entget GC50 (Rotation) in WCS and UCS

AutoLISP: MText: entget GC50 (Rotation) in WCS and UCS

Anonymous
Not applicable
907 Views
3 Replies
Message 1 of 4

AutoLISP: MText: entget GC50 (Rotation) in WCS and UCS

Anonymous
Not applicable
‎10-04-2018 02:11 AM

(Prologue:

I already discussed this on other forums, and I suppose that this an issue which Autodesk has to look after. So I opened a support ticket for AutoCAD (not on ADN), but my request was refused because "...they do not support Coding .. " and this is ... "why I have to post to this forum...". So lets see if I find a solution here.

End of Prologue)

-----------------------------

I thought that "entget" returns the DXF-values, based always on WCS. But now I compared the entget-data of a simple MText in WCS and in a simple UCS (moved and rotated), and it shows me that all values are the same - but GC50 (rotation) depends on the current UCS.

Is this a bug or a feature?

See the sorted DXF-values from two "entget" commands, one in WCS and one "UCS". I added the string "ucs" to show where the value come from.

(-1 . <Objektname: 15e20dfe5b0>)
(-1 . <Objektname: 15e20dfe5b0>) ucs
(0 . "MTEXT")
(0 . "MTEXT") ucs
(1 . "abc")
(1 . "abc") ucs
(10 -0.638118 1.82951 0.0)
(10 -0.638118 1.82951 0.0) ucs
(100 . "AcDbEntity")
(100 . "AcDbEntity") ucs
(100 . "AcDbMText")
(100 . "AcDbMText") ucs
(11 0.640061 0.768324 0.0)
(11 0.640061 0.768324 0.0) ucs
(210 0.0 0.0 1.0)
(210 0.0 0.0 1.0) ucs
(330 . <Objektname: 15e20e001f0>)
(330 . <Objektname: 15e20e001f0>) ucs
(40 . 2.5)
(40 . 2.5) ucs
(41 . 6.14396)
(41 . 6.14396) ucs
(410 . "Model")
(410 . "Model") ucs
(42 . 5.47237)
(42 . 5.47237) ucs
(43 . 2.54093)
(43 . 2.54093) ucs
(44 . 1.0)
(44 . 1.0)
(46 . 0.0)
(46 . 0.0) ucs
(5 . "293")
(5 . "293") ucs
(50 . 0.0664042) ucs
(50 . 0.876218)
(67 . 0)
(67 . 0) ucs
(7 . "Standard")
(7 . "Standard") ucs
(71 . 1)
(71 . 1) ucs
(72 . 5)
(72 . 5) ucs
(73 . 1)
(73 . 1) ucs
(8 . "0")
(8 . "0") ucs

---
Is this a bug or a feature?

0 Likes
Like
Report
908 Views
3 Replies
Replies (3)
Message 2 of 4

cadffm
Consultant
Consultant
‎10-04-2018 02:55 AM

I think the Value isn't a bug, the bug is that is

a) the bug is that is  to get groupcode 50

 or

b) the bug is that it is undocumented ("value based on ucs")

 

and c the "DXF-Reference" is wrong from the autodesks point of view, because in DXF gc50 is not part of a MText definition.

But it is allowd - MText gc11(21,31)

NOTE  A group code 50 (rotation angle in radians) passed as DXF input is converted to the equivalent direction vector (if both a code 50 and codes 11, 21, 31 are passed, the last one wins). This is provided as a convenience for conversions from text objects.

Sebastian

Report
Message 4 of 4

Anonymous
Not applicable
in reply to cadffm
‎10-04-2018 03:50 AM

For heavens sake - discussions staring in 2002 and 2003. We see the priority of Autodesk ..

 

So let's say:

 

a) yes, it is as described

b) nobody knows exactly why

c) The behaviour and the "Why" is not (or only confusing) documented.

 

So let's wait if Autodesk will confirm here:

"Yes, we see the problem and we will refresh or documentation."

 

BTW: Bricscad does not have the confusion - it shows GC50 always related to WCS

0 Likes
Like
Report
Report a website issue