Opened 8 years ago
Last modified 5 years ago
#14965 new enhancement
Improve autofilters
Reported by: | Don-vip | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core | Version: | |
Keywords: | autofilter | Cc: |
Description (last modified by )
Autofilters have been implemented in #14929.
The feature can be enhanced:
- allow users to define their auto filters through the filter dialog
- ✅ provide better/faster access to change the current autofilter (maybe in the visibility menu of the layer panel) → #18628
- ✅ allow values with units → #18679
- allow non-numeric values
- remove the zoom parameter?
- ✅ document the whole thing on the wiki - Done.
- ✅ see #17436
Attachments (1)
Change History (19)
comment:1 by , 8 years ago
comment:2 by , 8 years ago
The layer autofilter shows only the specific layer selected and does not work with multiple values.
For instance when 1 is selected, then objects with layer=1 will show, but objects with layer=1;2 or 1-2 will not.
Great new feature though - very helpful.
comment:3 by , 8 years ago
Creating new objects with an autofilter enabled is impossible: they immediately disappear, since they don't have the tag. Maybe the autofilter should include also new untagged objects.
comment:5 by , 6 years ago
Description: | modified (diff) |
---|
comment:6 by , 6 years ago
The zoom parameter doesn't work as expected. After you once reach the min zoom the filterbuttons are displayed and they stay there even if you zoom out. The only way to disable them is to zoom out, move data out of the mapview and zoom in.
by , 6 years ago
Attachment: | AutoFilterRule.java.patch added |
---|
follow-ups: 10 11 comment:7 by , 6 years ago
Here is a small patch that adds some more keys as autofilters and a space before the [
(for prettiness).
However buildings:levels
doesn't work. When activating an error pops up. It seems the :
marks the end of the key and puts e.g. :levels=3
into the value. I tried "building\:levels"
, "building\\:levels"
and "building" + ':' + "levels"
but none worked without compiling or UI errors...
incline
doesn't work as well, (I copied the syntax from maxspeed
), maybe %
has special powers here too.
So, if someone please could review before commiting that would be nice :)
comment:8 by , 6 years ago
Description: | modified (diff) |
---|
comment:9 by , 6 years ago
Summary: | Improve autofilters → Improve autofilters [patch needs review] |
---|
comment:10 by , 5 years ago
Description: | modified (diff) |
---|---|
Milestone: | → 20.02 |
comment:11 by , 5 years ago
Replying to Klumbumbus:
Here is a small patch that adds some more keys as autofilters and a space before the
[
(for prettiness).
You could simplify + " " + '[' +
to + " [" +
– feel free to apply your own patch.
follow-up: 14 comment:13 by , 5 years ago
Ah, sorry, I overlooked that.
The building:levels
problem is gone due to r15764. Previously, the string was compiled as a search expression, thus, new AutoFilterRule("\"building:levels\"", 17)
should have worked.
I'll look into incline=...%
…
comment:14 by , 5 years ago
Replying to simon04:
I'll look into
incline=...%
…
→ #18679 (including attachment:AutoFilterRule.java.patch)
comment:15 by , 5 years ago
Description: | modified (diff) |
---|---|
Summary: | Improve autofilters [patch needs review] → Improve autofilters |
Support for incline=20%
, i.e., value plus unit, has been integrated via #18679.
comment:16 by , 5 years ago
Description: | modified (diff) |
---|---|
Milestone: | 20.02 |
comment:17 by , 5 years ago
Description: | modified (diff) |
---|
I startet docu at Help/Dialog/Filter#Autofilters and Help/Preferences/Display#OSMData