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: layout dxl generator to display attributes from linked modules
Topic Summary:
Created On: 7-Aug-2003 08:20
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.
Answer This question was answered by , on Monday, August 11, 2003 4:03 PM

Answer:
Many thanks Louie for the hint it is working perfectly now

Cheers again

Faris Muhammad
Racal Instruments
 7-Aug-2003 15:06
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

I browsed the code for just a minute, but I notice that you are using the "for module in project do" loop. This only finds currently opened modules. If you intend to find ALL modules in the project, try this:

<<Start Edited Correction>>
Oops, I now notice the loop used was the "for ModuleName in Project do", incorrectly titled "for all modules in project". As specified, this loop ONLY finds modules in the top level folder of the project. In DOORS v4, there was no folder hierarchy so this loop DID find all modules in the project. Not so in v5/v6. Use the code below.
<< End Edited Correction>>

Item itm
for itm in prj do
{ if (type(itm) != "Formal") continue
NameMod = fullName(itm)
// deal with this module
}

- Louie


Edited: 7-Aug-2003 at 16:03 by Louie Landale
Report this to a Moderator Report this to a Moderator
 15-Aug-2003 14:31
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

The command "string source(link)" is useless (as is "string target(link)") since, as specified, it returns the unqualified name of the source module. When you try to open that module it only works when its in the "current" folder, as you have found out. (Likewise the "for all sources" loop is useless).

To get the full name of the source module, use the command immediately following which is
"ModName_ source(link)". In DXL, this translates to "string SourceFullName = fullName(source(link))". This returns the fullName which is useful when opening the module.

You need to pay attention to references to "unqualified" names in the DXL help, which means just the "base" name of the item without any folder hierarchy. Its like telling windows to run the unqualified name "doors.exe", but it cannot find it. You need to tell windows to run the full name "c:\Program Files\Telelogic\DOORS 6\bin\DOORS.exe". IUnqualified names have some use in reports such as "... running DOORS.exe" but are worthless within the workings of a DXL program.

Scribble this stuff down in your DXL manual hard copy, and when you print the v7 DXL manual transcribe it there.

- Louie
Report this to a Moderator Report this to a Moderator
 16-Oct-2003 17:51
User is offline View Users Profile Print this message


Linda Kidd

Posts: 3
Joined: 26-Sep-2002

Hi,

In relation to this dxl, I am looking for something a little more complex.
In version 6,

I need to be able to pull in links four modules down.

Example:

These are all incoming links of requirements

spec <-- Element <-- CRS Spec <-- HRS Spec

So a display column would have requirements linked from the CRS Spec in the main spec.

Is this at all possible.

Thanks
Linda
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.