Is there a way to get the current Filter?

Mathias Mamsch - Thu Mar 22 20:20:19 EDT 2012

How about: Filter current ()? Regarding the getAttributeFilterSettings: You probably need to experiment. My guess is, they will give you the settings for a simple filter to be applied, e.g. the first argument the attribute name, the second argument the operator, etc.

There are new perms for DOORS 9 however:
 

Filter getComponentFilter_ (Filter, int index)
int getCompoundFilterType_ (Filter)
string getProperty (Filter, string)
void setProperty (Filter, string key, string value)

 

which probably will allow you to modify compound filters. I did not look at the properties yet however, so at the moment I cannot tell you more. Maybe that helps, regards, Mathias

 

 

 

---

Mathias Mamsch, IT-QBase GmbH, Consultant for Requirement Engineering and D00RS

 

 

Mathias Mamsch - Thu Mar 22 20:20:19 EDT 2012

How about: Filter current ()? Regarding the getAttributeFilterSettings: You probably need to experiment. My guess is, they will give you the settings for a simple filter to be applied, e.g. the first argument the attribute name, the second argument the operator, etc.

There are new perms for DOORS 9 however:
 

Filter getComponentFilter_ (Filter, int index)
int getCompoundFilterType_ (Filter)
string getProperty (Filter, string)
void setProperty (Filter, string key, string value)

 

which probably will allow you to modify compound filters. I did not look at the properties yet however, so at the moment I cannot tell you more. Maybe that helps, regards, Mathias

 

 

 

---

Mathias Mamsch, IT-QBase GmbH, Consultant for Requirement Engineering and D00RS

 

 

Filter currentFilter = (Filter current());

Filter acceptAllFilter = attribute "Absolute Number" != "-1";

SystemAdmin - Fri Mar 23 15:31:48 EDT 2012

Mathias, for my specific needs, the below works fine:
 

Filter currentFilter = (Filter current());

 

My objective was to start with a clean slate and have users be able to add a few subtrees to the composite filter.

Once done, users can export (or do something else with) the filtered rows.

The append subtrees algorithm is basically:

For as many subtrees the user desires:

 

 

• Users selects a subtree
• If the current filter is null
  • set filter to the subtree
• Otherwise
  • set the filter = filter || subtree

When you start DOORS there is no filter so it is null. I could not find a way to make the filter null again. I had to kludge an "effective clear". I used the expression

 

 

Filter acceptAllFilter = attribute "Absolute Number" != "-1";

Thereafter when appending subtrees to a filter I actually do:

For as many subtrees the user desires:

 

 

• Users selects a subtree
• If the current filter is null
  • set filter to the subtree
• If the stringOf current filter is "Absolute Number != -1"
  • set filter to the subtree
• Otherwise
  • set the filter = filter || subtree

Unless you know a more elegant way to clear the filter, I'll call it done.

Thanks again.

 

Mathias Mamsch - Fri Mar 23 15:59:19 EDT 2012
Well what would you do in DOORS module to see all objects? Would you define a filter Absolute Number != -1 ? Or would just just turn off filtering. Why would you care that the filter is not 'empty' again? Turn it off, if you care about saving it to a view, just disable it in the viewdef. Regards, Mathias

---

Mathias Mamsch, IT-QBase GmbH, Consultant for Requirement Engineering and D00RS

Filter acceptAllFilter = attribute "Absolute Number" != "-1"

SystemAdmin - Fri Mar 23 16:47:44 EDT 2012

The "use case" where this is needed is as follows:

Suppose before a meeting a user wants to export subtrees 2.1.2, 2.1.4, and 2.1.5 as (for example) an HTML document.

In the same session the user wants to export subtrees 3.1.2, 3.1.4, and 3.1.5 as (for example) an HTML document.

When you first go into DOORS, there is no filter so this is fine:
If filter is null

• filter = subtree expression

Else

• filter = filter || subtree expression

When you want to do another completely different set of subtrees, you would keep ORing onto the first filter (getting subtrees you no longer want).

Since I could not find a way to clear it, I set aside the pattern below to be a "virtual clear".

So if I see null or the pattern below I set the filter to a subtree expression, otherwise I OR onto the prior filter

The sole purpose of

 

Filter acceptAllFilter = attribute "Absolute Number" != "-1"

is to start fresh again.

 

llandale - Mon Mar 26 09:15:13 EDT 2012
The following is my understanding of what you are saying, and it seems reasonable.
Your dialog has 2 buttons:

1. Clear Filter
   • Ignore the current filter and define a new one, AbsNo = -1
2. Add sub-tree to current filter
   • get the current filter, and "or" it with the sub-tree filter

Alternatively as Mathias suggests, the Clear Filter could just turn filtering(off), and the Add button checks if filtering is on, either creating a new sub-tree filter or "or"ing it with the current filter.

I'd like to point out that the "current" filter has a value even when filtering is off; which gives a slight nod towards Mathias' as it allows the user to "reset" by turning off filtering via the module GUI.

I'm also rather curious as to your sub-tree filter. Perhaps your code requires the user to select the sub-tree and push your button, in which case I think your filter needs to be:

• get the paragraph "number" of the current object
• define a filter such that it
  • accepts the object if it exacly matches that paragraph number, or
  • is larger than that paragraph number suffixed with a period and
  • is smaller than that paragraph number+1.

Not sure I said that right. Anyway, the problem comes in because the paragraph numbers are string values yet you want them sorted as integers. If section "2" has 12 sub-sections, their paragraph numbers will sort alphabetically like this: "2.1". "2.10", "2.11", "2.12", "2.2", "2.3" ... "2.9". There was a post some time ago resolving this issue for DXL, but I'm not sure how that would work with a filter.

-Louie

llandale - Mon Mar 26 09:15:13 EDT 2012
The following is my understanding of what you are saying, and it seems reasonable.
Your dialog has 2 buttons:

1. Clear Filter
   • Ignore the current filter and define a new one, AbsNo = -1
2. Add sub-tree to current filter
   • get the current filter, and "or" it with the sub-tree filter

Alternatively as Mathias suggests, the Clear Filter could just turn filtering(off), and the Add button checks if filtering is on, either creating a new sub-tree filter or "or"ing it with the current filter.

I'd like to point out that the "current" filter has a value even when filtering is off; which gives a slight nod towards Mathias' as it allows the user to "reset" by turning off filtering via the module GUI.

I'm also rather curious as to your sub-tree filter. Perhaps your code requires the user to select the sub-tree and push your button, in which case I think your filter needs to be:

• get the paragraph "number" of the current object
• define a filter such that it
  • accepts the object if it exacly matches that paragraph number, or
  • is larger than that paragraph number suffixed with a period and
  • is smaller than that paragraph number+1.

Not sure I said that right. Anyway, the problem comes in because the paragraph numbers are string values yet you want them sorted as integers. If section "2" has 12 sub-sections, their paragraph numbers will sort alphabetically like this: "2.1". "2.10", "2.11", "2.12", "2.2", "2.3" ... "2.9". There was a post some time ago resolving this issue for DXL, but I'm not sure how that would work with a filter.

-Louie

"Object Number" >= "A.B.C" 
AND 
"Object Number" < "A.B.(C+1)"
// C+1 is computed as an integer and then converted to a string