V12 mtext setting
Anyone know if there is a setting in Mtext where it will retain the last text height used. For me it keeps reverting back to whatever height that is set for the regular text command. Thanks.
0
Comments
-
I think you're right - there seems to be some inconsistent behavior here.
No idea how autocad handles this, but text and mtext objects share the same text size property (groupcode 40), so IMHO their initial size should equally be determined by the TEXTSIZE variable, and both should update this variable to the last value that the user entered.
Things are slightly more complicated because the textsize dropdown in the mtext editor has dual functionality (as far as I understand):
- if the input is empty, it will set the textsize property (and so should also update the TEXTSIZE var)
- if there is already text entered, it will just insert formatting code (which should not affect the TEXTSIZE var).
Maybe you should file a SR to get this sorted out...0 -
From my point of view I think that happening because MTEXT form is PRIVATE, I think it have to be PUBLIC and MTEXT (doesn't have to change TEXTSTYLE var).It is not only mtext height, and color of mtext is reset to default properties.You should send SR0
-
yes, using the style dropdown always results in an object property (groupcode 7) and thus should set TEXTSTYLE - but (as for TEXTSIZE) only if the editor has been invoked by the mtext command, not if editing an existing mtext object.
The color dropdown always results in embedded formatting, and should certainly not affect CECOLOR.
But all this seems slightly overcomplicated to me - I think I would prefer the mtexteditor to not set object properties, but just do formatting. TEXTSIZE and TEXTSTYLE would then only be set through the commandline options, and object properties only changed via the properties bar.
If the mtext GUI should remember the last used settings for the editing session (unrelated to any variables) is another story - most users will probably expect this, but it doesn't really bother me.0
This discussion has been closed.