![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: "for o in mod" in baseline module Topic Summary: When using "load" to open a past baseline, "for o in mod" loop breaks Created On: 29-Jun-2006 00:21 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hi All,
I have a basic function that counts the number of modified requirement objects that were changed btween given dates in a particular baseline. When I open the module in question, then open the baseline so that it is visible, the script works fine, but when I run the scipt and specify a different baseline than the one currently open, the script returns a 0. I've attached the function along with a couple lines that set up the arguments and call the function. I've taken out my debug code which allowed me to see that the correct ModuleVersion was "loaded". I want to "read" a module without displaying it, and have it opened to a specified baseline. according to the help file, "load" does just that. (type in "load(ModuleVerison)" in the DXL Reference Index) Any clues? Thanks! Jason |
|
![]() |
|
![]() |
|
Hi Jason,
you should try to use for o in entire mod do { if (!isDeleted o) { .... } } May be this will help to solve your problem. Doors is sometimes a little bit strange. Many functions will work on currently used view, so if you load a module in background you won't have any view. Greetings Reik Schröder ------------------------- Evosoft GmbH for Siemens Industry Sector Berlin, Germany |
|
![]() |
|
![]() |
|
As Reik pointed out, routinely use "for o in entire mod do"; if (isDeleted(o)) continue" construct for all your object loops. This deals with the cases the module has some filter or leveling that hides objects; which is especially important for modules opened visibly (and have a default view).
Sorry I haven't dealt with module version stuff yet in DXL. But it sure seems to me that your "load(modver, false) command should return some handle that should be used; probably "Module mBase". It looks to me that your script is searching history of the current module instead of one of the baselines. Shouldn't your loop be "for o in entire mBase do"? The only way two baselines could have History for a given date range is when the baseline is created during that range. If the create date of a baseline is before your startDate, and the next baseline was created after your endDate, then only one baseline will have history you care about. - Louie |
|
![]() |
|
![]() |
|
Thanks for your replies. I am actually trying to look at histories in specific baselines, not just deleted Objects in the most recent baseline.
My question can reduce to this: Using DXL, how can I open a particular baseline of a module? Thanks! Jason |
|
![]() |
|
![]() |
|
Change to the following:
Baseline bl = baseline(6,0,null) Module baseMod = load(bl, false) Date d1 = "01 aug 2002", d2 = "01 oct 2002" If (!null(baseMod )) { print changedCount(baseMod , bl, d1, d2) } The difference is using baseMod instead of mod. ------------------------- Shawn Stepper shawn.e.stepper@wellsfargo.com |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
"for o in mod" in baseline module
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.