![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: DXL filtering Topic Summary: Difference between "accept" and "includeCurrent" Created On: 4-Jul-2007 15:58 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
I am intending to write a DXL filter that uses the "accept" perm to define a filter to include certain objects but I'm unclear about the intended use of "accept" versus "includeCurrent". Presumably "accept" allows the addition of known objects to a filter, whereas "includeCurrent" would require each wanted object to be made current beforehand? If I define a filter using "accept" statements, it appears those objects remain on a filter list. Where is the list maintained and how do I clear it? Does each object that was previously named in an "accept" statement have to be named in a "reject" statement?
I'm using DOORS 8.1. ------------------------- Jim Backus<BR>Ultra Electronics, Controls |
|
![]() |
|
![]() |
|
includeCurrent is used as follows:
Filter f = includeCurrent set(f) filtering on This creates a filter that includes the current object. This is the same as selecting the "include current object" option in the GUI. You are correct in saying that each object would have to be selected, then this option selected and each filter would need to be added to the advanced filter and then combined using AND etc etc.... This is really not much use in a DXL script. The accept and reject perms allow you to create a "DXL filter" within a script. These filters cannot be saved in a view. You do not have to explicitly exclude objects using reject unless they have previously been accepted. The accept and reject settings persist beyond the execution of the script. ------------------------- Tony Goodman http://www.smartdxl.com |
|
![]() |
|
![]() |
|
Its not that clear in the manual, but there are fundamentally two kinds of Filters [1] Those that use a Filter variable are are eligible to be saved in a view [2] Those that don't use a Filter variable and cannot be saved in a view. This type features 'accept' and 'reject' commands.
I think its odd, but its worked out that I have yet to write type [1] and all my filters are type [2]. See attached for an example. If you fail to consider objects in the 'entire' module then I'm not sure what will happen for objects that you fail to accept or reject, perhaps the lingering filter's criteria appy. When you run a filter and then change an object which changes its filter status (such as undeleting it) and then turn filtering off and then on, [1] The filter recognizes the object's new status [2] The filter doesn't recognize the new status; you need to rerun the Filter to update the status of the object. Understand that accept and reject commands won't work correctly in a Layout or AttrDXL. - Louie |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
DXL filtering
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.