Display full version of the post: All text turns into hollow rectangles?

AmarARCH
11.07.2012, 17:13
I was having some fatal errors  so I restarted my computer and, after opening my original .dwg file,  I started having the issue: each text item is a hollow rectangle from the title block (Xref) text to even the Mtext or dimensions on the sheet's details (paper & model space).
 
Not sure how or what started this epidemic, but it appears that a few terminals in our office have started showing this same error and was sporadically showing up on rare occassions in the past. I think the previous fix was to ignore it until it goes away. Not happenning, here.
 
The text will show up perfectly if I double-click on it, so I can work on it.. but you can imagine how this cannot continue.
 
AutoCAD 2013 LT
Windows XP (mine)
Windows 7 (others)AmarARCH2012-07-11 17:22:42

John Connor
11.07.2012, 18:09
Check your QTEXT variable and make sure it is set to OFF then do a REGEN.What happens?


AmarARCH
11.07.2012, 18:16
It makes me do this:   THANKS!!

John Connor
12.07.2012, 12:27
Another lucky guess.You're welcomed.


Breeze104
12.07.2012, 14:46


The question now becomes ....Why is it affecting other computers.....if nobody changed anything????

John Connor
12.07.2012, 16:43
Maybe it has something to do with a custom lisp routine.


AmarARCH
13.07.2012, 14:37
Would you be surprised if I said "Ignorance is bliss"? Some folks wait for others to find the fix. Sure enough, I perked up and asked the question, and they come out of the woodwork with the same issue..
Would it be a factor if 80% of our office upgraded from 2000 to 2013 recently?
Since upgrading, there's been a small handful of "huh?" moments. For example, and I've yet to find a fix for this one: Why do I have to constantly turn the IMAGEFRAME to 0 each time I log into certain sheets, and, on certain sheets, the setting is already at 0 so I have to reset it to 3 then back to 0.. nuts! My best guess is there are certain settings that may be new to this upgraded experience, but we're too busy to go through a formal tutorial.
 
All in all, I'm loving the new CAD. But, yeah, a few head scratchers.AmarARCH2012-07-13 14:44:07

John Connor
13.07.2012, 17:52
If the issue is related to a system variable you could handle it with a short piece of code.  Example:

Normal
0




false
false
false

EN-US
X-NONE
X-NONE













MicrosoftInternetExplorer4



























































































































































/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}






(setvar “MaxHatch” 100000)


Breeze104
13.07.2012, 18:46



When I got the email that someone had replied to this thread and I looked at it I thought you were making a joke for a min about the short piece of code... Because I got about 2 pages of code....so I came here to see if what I got was actually what you wrote...LOL Good thing I did, cuz the code here is much shorter...LOL What I got looked like this (but 2 pages worth)....Which I am guessing wasn't your intent John...LOL Normal 0
<w:PunctuationKerning/> false
<w:IgnoreMixedContent>false</w:IgnoreMixedContent> false
<w:DonotPromoteQF/> EN-US X-NONE X-NONE <w:DontGrowAutofit/>
<w:DontVertAlignCellWithSp/> <w:DontBreakConstrainedForcedTables/>
<w:DontVertAlignInTxbx/> MicrosoftInternetExplorer4 <w:LsdException
Locked="false" Priority="0" Semi="false"
UnhideWhenUsed="false" Qat="true"
Name="Normal"/> <w:LsdException Locked="false"
Priority="9" Semi="false" UnhideWhenUsed="false"
Qat="true" Name="ing 1"/> <w:LsdException
Locked="false" Priority="9" Qat="true"
Name="ing 2"/> <w:LsdException Locked="false"
Priority="9" Qat="true" Name="ing 3"/>
<w:LsdException Locked="false" Priority="9"
Qat="true" Name="ing 4"/> <w:LsdException
Locked="false" Priority="9" Qat="true"
Name="ing 5"/> <w:LsdException Locked="false"
Priority="9" Qat="true" Name="ing 6"/>
<w:LsdException Locked="false" Priority="9"
Qat="true" Name="ing 7"/> <w:LsdException Locked="false"
Priority="9" Qat="true" Name="ing 8"/>
<w:LsdException Locked="false" Priority="9" Qat="true"
Name="ing 9"/> <w:LsdException Locked="false"
Priority="39" Name="toc 1"/> <w:LsdException
Locked="false" Priority="39" Name="toc 2"/>
<w:LsdException Locked="false" Priority="39"
Name="toc 3"/> <w:LsdException Locked="false"
Breeze1042012-07-13 18:48:14

John Connor
13.07.2012, 20:47
No, that was not my intent.  I was just showing you an example.