![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Trying to load "Standard view" without it being displayed Topic Summary: Created On: 9-May-2006 17:33 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: Thanks Ron and Louie! You were both correct. I added "entire" to my script and now it analyzes all objects, bypassing any filter the user has defined in the default module. I tested it a number of times and it provided consistent results every time. This was very important, as the script performs our Requirements Volatility measurements. Thanks, Tim | |
![]() |
|
Hello,
Below is a snippet of code which loads all formal modules, one at a time, in a specified project for some analysis. The problem I am having is that if I specify "false" on line three (to not display the module on the screen), the code ends up analyzing the default view instead of the "Standard view" view. What I would like to do is to be able to change line three back to "false" so that the user does not see any of the modules being loaded. Any ideas? Thanks in advance, Tim ... 1) for itemref in p do { 2) if (type itemref == "Formal") { 3) Module m = read(fullName itemref, true) 4) string viewName = "Standard view" 5) load view viewName 6) current = m ... |
|
![]() |
|
![]() |
|
Load view doesn't work if you do not display the module.
To process all non-deleted objects use the for o all in m do {} construct |
|
![]() |
|
![]() |
|
As Ron suggests it appears you prefer the standard view in order to have confidence in your "for obj in mod do" loop. That's a tricky loop. I ONLY use it when the script is designed to respect the current display set, such as when I put Next and Prev buttons on a dialog that displays an object.
As you've noticed, opening a module visible is VERY slow compared to opening it invisibly. Use "Entire": Depending on the current display is very problematic. Routinely use the "for obj in entire mod do" loop. This gets all the objects regardless of the current display set. The next line is typically "if (isDeleted(obj)) continue". Exclude other objects, perhaps with "if (cell(obj) or row(obj) or table(obj)) continue", to not consider an object associated with a DOORS table. If you prefer to consider only objects that qualify for a particular filter then you can manually calculate the filter for each object: if (null obj.NameAttr "") continue" - Louie |
|
![]() |
|
![]() |
|
Thanks Ron and Louie!
You were both correct. I added "entire" to my script and now it analyzes all objects, bypassing any filter the user has defined in the default module. I tested it a number of times and it provided consistent results every time. This was very important, as the script performs our Requirements Volatility measurements. Thanks, Tim |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.