Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic DOORS (steve huntington)
Decrease font size
Increase font size
Topic Title: Traceability Printing Problems
Topic Summary:
Created On: 27-Aug-2003 16:01
Status: Post and Reply
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
Quick Reply Quick Reply
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
 27-Aug-2003 16:01
User is offline View Users Profile Print this message


Patrick Turner

Posts: 1
Joined: 2-May-2003

I am having a problem with printing requirement document after doing a traceability analysis with both parent and grandparent selected (2 or more in depth). Toward the middle of the document to the botton of the pages, the requirements may be split and printed on the following page. Sometime, the previous requirements are printed again on the next page. I have tried many different print settings. With just traceability down one depth, it seems to print ok without print the same requirement twice. Thanks for any assistance in providing a presentable document to higher managerment and review panels.
Report this to a Moderator Report this to a Moderator
 24-Sep-2003 16:59
User is offline View Users Profile Print this message


Brian Azelborn

Posts: 36
Joined: 2-Dec-2002

This may not make any difference, but whenever we have trouble like you are describing with printing, one of the first things we try is to convert the layout DXL column into either an attribute DXL or a static copy of the text. Then redefine the view to show the information without layout DXLs. This often fixes the problem.

To re-define the layout DXL as an attribute DXL, you need to go through the layout DXL code and do the following:

1. Define a string variable to hold the trace information. For example:
string sResults

2. Look through the code for all occurrences of the word "display". Replace them with an assignment to your variable. For example:

Replace "display s"

with sResults = sResults "\n" s

This will append the new display line to the end of the previous displays

3. Assign the results variable to the attribute at the end of the script. For example:

obj."LayoutAttr" = sResults

This assumes your DXL Attribute is called "LayoutAttr"


Report this to a Moderator Report this to a Moderator
 24-Sep-2003 18:08
User is offline View Users Profile Print this message


Michael Sutherland

Posts: 248
Joined: 13-Sep-2002

Brian's advice is sound (as usual). A couple of minor points:

(1) For Attribute DXL, you can use the predefined constant:

obj.attrDXLName

The constant "attrDXLName" will automatically be set to the Attribute that the Attribute DXL is attached to. This make the code more portable, if you want to use reuse the code for other Attributes (there is a page about "attrDXLName" in the DXL reference manual).

(2) If performance is an issue, look into Buffers for accumulating the results to display.

-------------------------
Michael Sutherland
michael@galactic-solutions.com
http://galactic-solutions.com
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic DOORS forum.
There are currently 1 users logged in.
The most users ever online was 15 on 15-Jan-2009 at 16:36.
There are currently 0 guests browsing this forum, which makes a total of 1 users using this forum.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.