Wipeouts, and Textframes work in plan view and print preview, but show as disabled in PDF when printed. They are on the same layer as my text so it's not on Defpoints or some other frozen/vp freeze/no plot layer. They do print to DWF propperly though. It also doesn't matter what the frame setting or transparency settings are nothing seems to work for PDF. Any ideas?
Wipeouts have not behaved in PDF's for as long as I've used them. I've never found a solution but you might get some hits from Google.
If you are using them to mask text, have you tried the Autocad text backgound command?
I use it all the time, but this is a file from another engineering company, and there is <gasp> no mtext. I went ahead and printed to DWF and then printed that to PDF with no problems. I've had wipeouts worrk as recently as 2012, so i guess Autodesk is killing out the older legacy items one by one, huh?
In spite of the problematic behavior of wipeouts over the years, they do still serve a purpose aside from masking text.
There may be a free utility to convert DTEXT to MTEXT without lumping it all into a single piece of MTEXT. I believe Terry Dotson has such a tool in his DOTSOFT TOOLPAC tools.
This is a good case for an enhancement request.
Expresstools has a convert text to mtext command which i normally use, but i'm not going to waste a bunch of time converting some 400-500 callouts. I did use the DWG to PDF when creating the PDF, and i think that's where the problem lies. I tried printing directly to Adobe, and got a blank sheet after a 5 minute hang up when printing. Like i said earlier, it works when printing to DWF first, then printing to Adobe from the DWF.
I always use the CutePDF writer (free) to plot and CutePDF (inexpensive) to edit. There seem to be much less issues. I have wipeouts in block that plot with no trouble. I don't use them in regular drawing much anymore.
Well, if you ask me it's got something to do with autocad's image handeling. That's the base of any masking that autodesk uses with an exception to mtext masking. I also use wipeouts in some of my boundary pin blocks, and never had problems before 2013. I think there are some internal components that autodesk has yet to complete in the programming, so i'll just chock it up to autodesks constat "Work in progress" programming. Thanks for all the input guys, i'm going to submit another ticket about this...lol.
Just an FYI,
The TXT2MTXT command in Express tools lumps all the selected text into a single MTEXT object, which you don't want. To avoid that you would have to run the command on each piece of text, which obviously is not practical.
The DOTSOFT TOOLPAC tools have the ability to convert multiple pieces of text while leaving them as separate entities. It's not free though.
Allen, does Terry's TXT2MTXT LISP tool work the same as the Express Tool or does it preserve the pieces as separate entities?