Ticket #2841 (closed feature: fixed)
Filter strategy constructor should not need filter
| Reported by: | bartvde | Owned by: | fredj |
|---|---|---|---|
| Priority: | minor | Milestone: | 2.11 Release |
| Component: | Strategy.Filter | Version: | 2.10 |
| Keywords: | Cc: | ||
| State: | Commit |
Description (last modified by bartvde) (diff)
My use case is: at the startup of my application, I want to show all features. Then later on users can control the visibility of features by using checkboxes in a legend, so I will use setFilter then. However, now I have to instantiate my Filter strategy with something like (a filter that matches everything):
new OpenLayers.Strategy.Filter({
filter: new OpenLayers.Filter.Comparison({type: OpenLayers.Filter.Comparison.LIKE, property: 'categorie', value: ''})
})
How about allowing instantiating the strategy with no filter?
Attachments
Change History
Note: See
TracTickets for help on using
tickets.

