Topic Title

Hi All,

On previous versions of Dcad, I was able to turn the boundary box off when inserting or resizing paragraph text. Can't seem to find the setting on V 21. I have this line in my dcadwin.ini file- Show PText/MText Boundary On Entry/Resize=False. Whether true or false, the boundary box still shows. I REALLY don't like it Is there a setting somewhere else that I need to change? Thanks in advance.

Cheers,
Paul

When you input the Ptext or Mtext make sure boundary is deselected before you start the text

I think he is referring to the "fix" from Rev History
DataCAD 20.03.00 Fixes
18. The following DCADWIN.ini keys are no longer used as these settings have been
permanently set to TRUE.
[General]
KB4054518=TRUE
New Regen=TRUE
NewSymbolExtents=TRUE
Show PText/Mtext Boundary On Entry/Resize=TRUE

Personally I don't like the fix, but if it's a must, I would change defaults to make the boundary line color to match the screen background and live with it.

I agree with Roger about the box color matching the screen color if there has to be a box. Why would Dcad “fix” something that wasn’t broken? This is not a small item for me. It’s screen clutter. As I'm placing or resizing text, the boundary box gets really wide even though no text gets anywhere near the right and left boundaries of the box.

I’d like to know the reasoning behind it because it escapes me. This is not a fix. And, if the "lines below" are permanently set to True, then why are the lines still in the dcadwin.ini file that can be set t False?

the boundary box gets really wide even though no text gets anywhere near the right and left boundaries of the box. I’d like to know the reasoning behind it because it escapes me.

I would guess your margins are set really large.

And, if the "lines below" are permanently set to True, then why are the lines still in the dcadwin.ini file that can be set t False?

They don't delete the lines (I don't think) with the updates. I think they are just letting you know they are obsolete and can be removed by the user.

Ok, Josh, I'll bite. How do you change the margins? Never needed to know how to do it before since I never displayed the box. Still don't know how displaying the box is a fix. Would appreciate some input from Dcad here. Thanks.

How do you change the margins?

It's in the P/MText menus at position F3.

Thanks Josh. I really appreciate your help. I'll play with the settings.

If you don't need to have the text wrap, just a single line of text, just hit enter. So in PText, you've entered the text, Ctrl-enter/enter and you will not see the box.
Now if you need to resize or have the text wrap to multiple line, you will see the boundary box.

I do need the text to wrap, but thanks for the reply. Can anyone tell me why the box needs to be visible? It's worked just fine for years without it, so why the change?

[Mark F. Madura]

"I’d like to know the reasoning behind it because it escapes me. This is not a fix. And, if the "lines below" are permanently set to True, then why are the lines still in the dcadwin.ini file that can be set to False?"

The following key in DCADWIN.ini (along with several other documented and undocumented keys) was a casualty of cleaning up and removing outdated source code. When Dave and I discussed it at the time, we were both certain it would be 'helpful' to display the bounding box while PText and MText entities are being sized/re-sized. Obviously, we were mistaken. Now that the blame analysis is complete, the following key will be restored in the next update to DataCAD 21.

It's too bad no one noticed it three months ago in my original post for DataCAD 20.03.00 BETA 1 on December 08, 2018.

[General]
Show PText/MText Boundary On Entry/Resize=FALSE

FWIW, I did notice this new "feature" when first introduced.
I initially found the bounding box to be annoying, but after a few weeks, I have grown to love it and wouldn't work without it.
Always good to have the option however.

I too noticed it when it was done. I said nothing because it was a welcome addition. I have absolutely no problem with the way it was implemented.

Hi Paul,

What is it that you like about this? Perhaps I'm missing something here.

Cheers,
Paul