Lost standard grips for centered multiline text

[Paul Maxx]

Typically when I create multiline text using Middle Center Justification I would get grips in all four corners that I could then move to fit inside my object and the text would move along with it. Now when I create a piece of multiline text and try to move the grips I have and arrow grip to the right, an arrow below, and a standard grip in the middle. Also is I move the text a box appears around it.

 

I am assuming this is some sort of system variable but I have not been able to find it and have no idea how it could've be changed as it worked one second and didn't the next.

 

I opened up an older drawing and the existing Mtext had all four grips but any new text I created did not.

 

Any ideas? Any and all help is appreciated.

[BlackBox]

Congrats on your first post, and welcome to the forums!

 

Take a look at the 'Defined Width' and 'Defined Height' in the properties panel (with the MText selected)... I think you'll find them set to 0.0 in this case.

 

If you want those grips back, simply provide a value greater than 0.0...

 

Hope this helps!

[Paul Maxx]

Thanks RenderMan, but unfortunately this did not work. The "Defined Width" has a positive value but the "Defined Height" does not and it will not let me change the value from zero and just takes me to the QuickCalc. This is defintely a global issue as it effects all new text with any text style in both a new or pre-existing drawing.

[BlackBox]

Is your Mtext (or current Text Stlye) annotative, perhaps?

 

 

Edit: If you post a sample drawing, I might be able to offer more help.

[Paul Maxx]

I have attached a file with a sample of the issue. I used the Standard default text style for this. You can see the Defined Height is 0.00 and the odd grips and box when moving the text. Also it seems I cannot properly stretch the grips in Sample A to the ends of the blue box.

 

Please let me know what you think and thank you for your help.

Text Sample.dwg

[BlackBox]

Sorry, mate.

 

As you can see to the left, I am still using 2009... can you upload a copy saved back to 2007 file format?

[cpriedel]

the difference I see is the colums option. "Sample A" is set to None, "Sample B" is set to dynamic.

[Paul Maxx]

Sorry about that, here's a 2007 version.

Text Sample.dwg

[alanjt]

LISP to change width (since it pertains)...

 

(defun c:WD (/ ss wd)
 ;; Change width of selected MText and MultiLeader objects
 ;; Alan J. Thompson, 11.05.09
 (vl-load-com)
 (if (and (setq ss (ssget "_:L" '((0 . "MTEXT,MULTILEADER"))))
          (setq wd (initget 4)
                wd (cond ((getdist "\nWidth <0.0>: "))
                         (0.)
                   )
          )
     )
   (progn
     (vlax-for x (setq ss (vla-get-activeselectionset
                            (cond (*AcadDoc*)
                                  ((setq *AcadDoc* (vla-get-activedocument
                                                     (vlax-get-acad-object)
                                                   )
                                   )
                                  )
                            )
                          )
                 )
       (vl-catch-all-apply
         (function vlax-put-property)
         (list x
               (cond ((eq (vla-get-objectname x) "AcDbMText") 'Width)
                     ((eq (vla-get-objectname x) "AcDbMLeader") 'TextWidth)
               )
               wd
         )
       )
     )
     (vla-delete ss)
   )
 )
 (princ)
)

[BlackBox]

the difference I see is the colums option. "Sample A" is set to None, "Sample B" is set to dynamic.

 

Cpriedel is correct (great job!).

 

If you use the button [...] to the right of the columns row, and set to 'no columns' then your grips are restored.

[cpriedel]

type: MTEXTCOLUMN in command line and set value to "0"

Hope this helps

[Paul Maxx]

Thanks Cpriedel for catching that. But while that did solve the issue for that piece text, any new text I then create is defaulting to Dynamic Columns.

 

WOOHOO! Looks like I just found a system variable call MTEXTCOLUMN (in 2010 and 2011 only I beleive) that somehow got set to dynamic. I have set this to 0 and my grips are correct now.

 

I also fixed the grip issue moving to the corners with the CENTERMT variable. I had previously set it to 1 to see if that would fix my issue and just needed to put it back.

 

I am just left to wonder how in the world the column variable got changed to begin with when I am 100% sure I never typed it in. I am always amazed how some it seems sometimes variables just change due to some other seemingly unrelated action.

 

Thanks guys for helping me out on this! I hope I get the chance to repay your help by helping someone else out on the forum. Thanks again.

[Paul Maxx]

type: MTEXTCOLUMN in command line and set value to "0"

Hope this helps

 

I just saw your second post. I didn't notice the thread went to a second page already. Thanks again.

[BlackBox]

...

I am just left to wonder how in the world the column variable got changed to begin with when I am 100% sure I never typed it in.

...

 

Your statement assumes that the MTextColumn variable, by default, is set to your preference.

 

To test this, open a new drawing (based on your company's standard template), and check the variable...

• Is the variable set to 1 or 0 (your preferred setting)?
  

*IF* my speculation is correct that the setting is driven from your company template, see if your CAD Manager will adopt your setting instead. If they are not open to making this change, you can still 'force' this change programmatically by adding this to your ACADDOC.lsp:

 

(if (/= 0 (getvar 'mtextcolumn))
 (setvar 'mtextcolumn 0))

 

 

 

...

I am always amazed how some it seems sometimes variables just change due to some other seemingly unrelated action.

...

 

It only 'seems' that way... A cause unseen, is not proof that there is no cause... The observer simply requires enhanced observation. :wink:

 

If you notice that system variables are being changed often, this is likely to be cause by inadequate *error* checking in custom routines. (i.e., the routine may change variables at the beginning of the routine, and correctly change them back *IF* all goes well... but if there's an *error*, the changed variables are not restored)

 

Good luck!