![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: How to avoid newlines in WEXP output? Topic Summary: Created On: 23-Nov-2006 08:28 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hi, Can anyone help me with these problems, I'm not too familiar with dxl: 1. I have used the wizard to create traceability columns showing object ID's linked to for each user requirement. When I export the view to word using WEXP a newline appears between every object ID. I could use a word macro to go through and delete them but does anyone know of a change to the standard wizard dxl which could be done to stop the newlines occuring. 2. Is it possible to include para and header information in the traceability column for the object linked to. I wish to do this to put the object ID in context. The wizard provides only the information specific to the object linked to e.g. ID, text etc. The view I have in mind is near the back of the book "Requirements Engineering" by Jeremy Dick and others. I am using DOORS7.0 SP1 Thanks Adrian |
|
![]() |
|
![]() |
|
Adrian,
You can select as many attributes as you wish to display when using the wizard, note the list will vary if you specify all modules rather than a specific module, however each "display" command will place a new line at the end, ie each attribute will be reported on a new line. If you wish to use a different seperator between items then the best solution is to buffer the results then display them when the loop has completed. Here's a simple example using the same string. s = null for l in all(o -> linkModName) do {... ... s = (identifier othero) //displayRich s if (!null s) { s = s ", " s } } displayRich s - Martin ------------------------- - Martin |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
How to avoid newlines in WEXP output?
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.