AttributeRangeFilter returns main graph when nothing matches filter

Bug #823036 reported by Luiz Ribeiro
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Gephi
Confirmed
Undecided
Mathieu Bastian

Bug Description

When you apply a NodeAttributeRangeFilter with a given range that doesn't match any node (or edge, in the case of an EdgeAttributeRangeFilter), a GraphView which is equal to the original main graph is returned.

Here's an example code, suppose that all the nodes have the attributeColumn in the range [0, +inf[ (i.e. strictly positive):

AttributeRangeFilter filter = new
AttributeRangeBuilder.NodeAttributeRangeFilter(attributeColumn);
Query query = filterController.createQuery(filter);
// this shouldn't match any nodes
filter.setRange(new Range(-10, -5));
filterController.filterVisible(query);

Revision history for this message
Luiz Ribeiro (luizribeiro) wrote :

I have attached a JUnit Test class in which NodeAttributeRangeFilter fails several tests.

Changed in gephi:
milestone: none → 0.8alpha
assignee: nobody → Mathieu Bastian (mathieu.bastian)
Changed in gephi:
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.