Filter "Between" in a grid

[c0ff75]

Hello,

How to use filter "between" for a any field in the grid?

For example here:
http://www.smartclient.com/smartgwt/...perator_filter

I select filter "between" for "Area" field. In the field place I see a button with 3 dots. Where i should enter left and right value for "between" filter? I can't understand...

Please give me answer ;)

Best regards,
Eugeny

[Isomorphic]

We're looking into ways of dealing with this situation better.

In the meantime, you can just set grid.allowFilterExpressions: true, and then enter the full value in the editor - so, typing "1...100" into the editor will detect that its a "between" criteria and update the icon, but will not remove the "..." from the value, as it does with other operators - because there's no other way to enter a pair of separate range values.

We'll update here in the near future when we decide on the best framework-level solution.

[Blama]

Hi Isomorphic,

I have two comments to that sample as well:

• This does not show the criteria, but applies them:

isc.ListGrid.create({
    ID: "countryList",
    width:550, height:300, alternateRecordStyles:true, allowFilterExpressions: true,
    dataSource: worldDS,
    fields:[
        {name:"countryCode", width:50},
        {name:"countryName"},
        {name:"capital"},
        {name:"continent"},
        {name:"area"},
        {name:"population"}
    ],
    autoFetchData: true,
    showFilterEditor: true,
    allowFilterOperators: true,
    initialCriteria: { _constructor: "AdvancedCriteria", operator: "and",
        criteria: [
            { fieldName: "area", operator: "between", start: "10", end: "100" },
            { fieldName: "capital", operator: "iNotStartsWith", value: "p" }
        ]
    }
});

• The icon (text?) for the filtering mode is not displayed correctly in the filter row. It seems to be wider than the available space, at least for the 2-char operators:

This (closed) issue might be related.

Best regards
Blama

[Isomorphic]

Yes, this is true - we'll make sure incoming criteria are properly parsed in this case. Can you confirm, though, that using the UI to enter a "between"criteria works as described previously?

[Blama]

Yes, manually filtering for "1...100" gives me this expected result:


Best regards
Blama

[Isomorphic]

Actually, the problem is that "between" and "iBetween" are unavailable - if your criteria uses betweenInclusive/iBetweenInclusive instead, it will work as expected.

We'll look into that too.