Skip to main content
12-Amethyst
January 6, 2014
Question

Wrap Text in Tables

  • January 6, 2014
  • 16 replies
  • 7568 views

Whenever a user creates a new drawing, our formats are set up to use parameters from the model (of course).


Despite the addition of a Wrap Text option since WF5.0, it appears there is no way to get a table cell that contain a parameter to wrap text properly. Three software releases later.


When I asked about it, PTC, in their infinite wisdom, directed me to CS28238 which provides a solution of splitting the one parameter up into several different parameters and adding them all to the table cell, thereby allowing a portion of the parameter's contents to be displayed in each line. This, of course, is just a long way of saying, "Wrap text doesn't work at all in these cases." In short, they gave us a pseudo improvement.


In the meantime, the only solution I could come up with is to add a dummy column at the left and right ends of any table cell that will contain wrapped text (mostly just the Description cell in the title block). I can then put the parameter into the middle cell, hide the line between the cells and fake it.


Anyone else have a solution or thoughts on how best to handle this?


This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

16 replies

12-Amethyst
January 8, 2014

Erik,


We're not seeing either problem in our tables (Creo 2.0 M040). A sample is attached.


I experimented with dumb text and parameters and with different text justification. In all cases it seems to work as I would want. And I'm not aware of any configuration options that would affect table margins.

12-Amethyst
January 15, 2014

Mark,


I ended up opening a call with PTC tech support about this. From what we were able to determine, the automatic height adjustmentwithin merged cells will work fine with new tables on new drawings created in Creo 2. However, if it is a Pre-Creo drawing (in our case we're coming from WF4), neither new tables nor tables created from table files originating in WF4 will auto height adjust in merged cells.It also fails to work ina new in Creo 2 drawing when using a table file originating in WF4.PTC hasopened an SPR to investigate this.



Erik

23-Emerald III
January 15, 2014
That makes sense since the code change is in the table structure itself. Only new tables created in Creo2 would have the ability to wrap text.

I will not be surprised if R&D comes back with "working as designed".

It will take an enhancement request and an act of a Supreme Being to get the table functionality to update existing tables.


1-Visitor
January 15, 2014

The developers had a choice. They can update the table structure when they find an old one andcontinuewiththat or they can create anothertable structure to use in parallel with the old one(s).

They (presumably) will always have to read in the old structure(s) in order to read/modify old drawings. They will always use the latest table structure to create new tables.


If tables aren't being updated, then two things are possible - either PTC failed to update the tables as they intended to or PTC decided it was OK to make it harder on their customers and save a little development time to make updating the table structure work, and not including a message indicating "Old table not updated - Create new table to use new features."


Since the two outcomes look the same, I'm interested in which turns out to be true.

13-Aquamarine
January 15, 2014
Exactly what we found. The issue is you have to open up the tables and save them again so they work correctly.
The problem is, before m060, when we would bring up our drawing that had all the tables on it, Creo would crash when you tried to save out a table. That's the problem that was fixed in m060.

Our BOM tables are separate from the drawing template, so we just have to remove and insert again, but then of course you just lost all your filtering, and fixing of the index.

David Haigh
12-Amethyst
January 15, 2014

PTC came just got back to me on this confirming there is a bug. However, there is a workaround. So far it has worked for me.



To correct the issue:



  1. Open the drawing

  2. File > Prepare > Drawing Properties > Detail Options change

  3. Add option as update_drawing and value as 2069392 > Add/Change > Ok

  4. Review> Update sheets > Update tables


Erik