Anuncios

The Autodesk Community Forums has a new look. Read more about what's changed on the Community Announcements board.

kzD1219
5304 Vistas, 9 Respuestas

Mtext Justification grip location

I am setting up old text to mtext.  I want to keep the new mtext in line and spaced evenly.  I have the justification to the Bottom left however I end up with the image attached. How do I get the grips to all be at the same location of the mtext?  See how some grips are at the text and others are a little below?  Any way to fix that?

TheCADnoob
en respuesta a: kzD1219

Use TEXTALIGN

 

First it will do the vertical but you can select options and then choose spacing. 

 

 

CADnoob

EESignature

kzD1219
en respuesta a: TheCADnoob

That is a nice command, but we rely heavily on the grip location since we use that spacing and location for things like a legend.  This attached image shows how the text lines up with a pre-made grid. I know I can grab a piece of text at a grip and move it spaced out evenly within grid.

 

I am looking to update text to mtext on templates I am working on, however is text just as good in a situation like this?

pendean
en respuesta a: kzD1219

Why aren't you using a table (with invisible lines) if alignment in legends is so critical? That's how we all do it, relying on floating objects to always perfectly align is not a good way to do it.

Why the move from TEXT to MTEXT? The latter is not an upgrade, the former is not going away ever.
kzD1219
en respuesta a: pendean

I never set up these legends, so I am not sure why they didn't go with tables.  Good suggestion though.  

 

But thanks for your opinion on text and mtext.  I will probably keep items as text since mtext is giving me a hassle.

TheCADnoob
en respuesta a: kzD1219

use the tools for the job they are intended for. 

 

if these are bound in a gird and only going to be single line text i would imagine multiline text (MTEXT) is overkill

 

That said pay attention to the drawing specs/standards. your company, or your client may require a different type of text for different reasons. 

CADnoob

EESignature

Kent1Cooper
en respuesta a: kzD1219

This is a drawback of Mtext, in my opinion, if plain Text will serve your purpose.  It's because of descenders, i.e. the lower-case y that appears in your image, and I would bet that the other ones with the grip below the base-line also have y or g or j or p or q or / or ( or ) or some other character(s) that descend(s) below the base-line.

 

Zoom in close and start an Mtext command, get into Bottom-Left justification, and slowly type in the word testing.  Notice that the position shifts  as soon as you get to the g -- now the bottom of the object is below the base-line, but the justification uses that bottom of the object.

 

If you use plain Text, and use [single-word] Left or Center or Right [or Aligned or Fit] justification, not Bottom-Left, etc., then the insertion point will be at the base-line, whether or not there are any descenders.  Mtext does not have those single-word justification options that plain Text has.

 

Oddly, though, in plain Text, if you use [for example] Bottom-Left justification, it puts the base-line raised as might  be required by descenders, even if there are no descenders  in the content.  Annoying but at least consistent -- Mtext only does that shift if there are  descenders involved, so the same object can have its position shifted just by changing one character of its content.

Kent Cooper, AIA
kzD1219
en respuesta a: Kent1Cooper

Yes I noticed that about the descenders.  Text will have to be my go to for now I guess.

TheCADnoob
en respuesta a: Kent1Cooper

In properties, try changing the line space style from at least to exactly if you want to stick with mtext and see if it helps

 

CADnoob line space style1.png

CADnoob

EESignature

Kent1Cooper
en respuesta a: TheCADnoob


@TheCADnoob wrote:

In properties, try changing the line space style from at least to exactly if you want to stick with mtext and see if it helps

 


I tried that, but it doesn't.  I do my Mtext that way for other but related purposes, but it doesn't get around the difference between a bottom line of Mtext that has or does not have descenders.

Kent Cooper, AIA