![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: How to Make "Non-Main" Column Take on Word Style During Export Topic Summary: Created On: 19-May-2008 17:22 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hello,
We have projects whose customers are requesting red-lined documents. (The red-lines would show the changes since the last time the document was delivered.) I experimented with the attached code (I am not the author) and modified it to generate a layout dxl column that shows the correct markups. However, when I export this column, the text does not take on the Word style associated with it. It is all in the Normal style. My question is how can I make a "Non-main" (not the actual Object Heading and Object Text column) take on Word styles for purposes of exporting? I realize one could always export the newer revision of the module and perform a Document Comparison in Microsoft Word but I am hoping to eliminate the extra steps required for that process. Any help would be greatly appreciated. Regards, Tim |
|
![]() |
|
![]() |
|
Cannot help with the export problem.
Code observation: you really should delete Buffers after using them. If a function returns a Buffer as the return parameter, then the caller should do something like this: Buffer bufRet = MyFunction(o, params) use bufRet delete(bufRet) Putting the 'delete(buf)' command after the 'return(buf)' command doesn't work, since no code is executed in the function after the 'return' statement. - Louie |
|
![]() |
|
![]() |
|
Not sure how the exporter works, but...
You can't read richText from columns but you can from Text attributes. Try: Convert your layout DXL to Attribute DXL. Replace the column with a new attribute column. ------------------------- Tony Goodman Smart DXL limited www.smartdxl.com |
|
![]() |
|
![]() |
|
The "easiest" way to go is with pdf print of the view.
|
|
![]() |
|
![]() |
|
Heh... I ran into this with my baseline comparision script. What we did is create a Word Macro to look for the underline/strike through and color code the text based on that; blue for underline, red for strike through. Works pretty well for us, and I just call the macro after my export.
*Edit* Heh...here's the macro we use. ------------------------- Scott Boisvert Engineering Tools Administrator L-3 Communications - Avionics Systems scott.boisvert@l-3com.com Edited: 20-May-2008 at 13:40 by Scott Boisvert |
|
![]() |
|
![]() |
|
I used to try to do this in DXCL. Comparing each Attribute as needed...
Turned into a pain to keep up w/ new modules.... etc... A few years ago I found another way to do this. Using a word document compare package called Workshare Deltaview. It does a great job creating RedLine word document compares. I have used it to compare documents well over 1000 pages in length and had it work very well. I has a tendency to get mixed up on very large Tables but other than that it id dead accurate and saves mucho time. Our simple process.... We save each exported Word.doc for release into ClearCase. The next version exported (months - years later) is exported and compared aginst the last release in ClearCase. Simple, Fast and effective. |
|
![]() |
|
![]() |
|
The easiest way to do what the original poster requested is to generate a document from the baseline, and then generate a document from the current. Then do a "Compare Changes using Legal Blackline" in Word.
The steps to do the Compare Changes are different depending upon which version of Word you use, but it's usually around Tools>Track Changes.... ------------------------- Kevin Murphy http://www.baselinesinc.com |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.