![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Louie's TidBit #4: Manual Filters Topic Summary: Created On: 7-Oct-2003 17:24 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
There are two basic ways to write filter scripts
[1] define a filter using the various commands in the Filter chapter, ending in the "set(filter)" command. E.G. You can define such a filter to display all Object Text containing "shall". This sort of filter IS saveable in a view. [2] You can decide on a criteria and evaluate it for each object: ... filtering off ... for obj in entire mCurr do ... { if (this object matches my desired criteria) ....... accept(obj) .......else reject (obj) ... } ... current = mCurr ... filtering on ... refresh(mCurr) This sort of filter is NOT saveable in a view. However, you can generally do much more complicated filters this way, such as if an object is "Allocated" to a subordinate module, is there at least one incoming link from that subordinate module. Some natural adjustments to the above are [a] supress the first "filtering off". Thus, the script works on the current display set (e.g. it restricts the current display set) count the number of accepts/rejects, and ack them to the user when done. I like this method when it works on the current display set. I have several such "simple" filters in the menu, and can easily mix and match them to get where I want. - Louie Edited: 7-Oct-2003 at 18:45 by Louie Landale |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
Louie's TidBit #4: Manual Filters
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.