Page 1 of 1

MText DWG Export Boundry Glitch

PostPosted: Thu Mar 17, 2016 1:46 pm
by joshhuggins
Not trying to sound snarky here, but is there any hope that this MText wrap point issue will ever be addressed/fixed? Have been reporting it since v.12 and don't recall ever actually receiving a response on this issue so I don't know if it's actually something that might be fixable, something that can't be fixed in the DWG translator, or something we are doing wrong on our end. Co-workers have some pretty peeved off clients right now because of all the extra work they are having to do to send DWG files that will actually represent their Datacad counterparts. Exploding the Mtext before export helps, but not so much when there is MText withing tons of symbols in the drawing. :? Would be nice to be able to send the MText intact so they can use it also on the clients end instead of futzing with single line text.

MText in Datacad
dcmtext.PNG


MText in Trueview
tvmtext.PNG

Re: MText DWG Export Boundry Glitch

PostPosted: Fri Mar 18, 2016 7:56 am
by jimgoodman
We would appreciate a fix for this as well.

Re: MText DWG Export Boundry Glitch

PostPosted: Mon Apr 04, 2016 3:02 pm
by joshhuggins
Was thinking about this as I was in the process of exploding/exporting a bunch of GTV's and even if we could get just a check box in the export dialog to explodes all MText/Symbol Mtext while exporting DWGs that would be a big help if that was easier to do for now. Still need to fix a lot of the exploded text in Autocad after, but at least it would save us some time on the front end.