Any chance more advanced filtering?
this is something I was already thinking some time ago. In the end, I've prepared a little bit "overkill" solution (not for everyone) that may anyway allow very robust filtering.
So in the next big app version, points and tracks filters allow defining filter names over regular expressions.
If you are not familiar with this system, I'll gladly help here in this topic once version will be published, so let me know.
Second, any thoughts to extrend regex support from filtering to search, which is also working across all folders?
Best regards, Georg
hmm seems there is tiny issue, thanks for this discovery. I'm just preparing new version so please check it once you receive an update, thanks.
I get filtering with RegEx running in Locus 4.10.0 🙂 By try & error I learned the syntax is very close to http://www.w3.org/TR/xpath-functions/#regex-syntax and http://www.w3.org/TR/xmlschema-2/#regexs Not only the original requested filter possibility but even much more sophisticated stuff is possible 👍 Some findings. @Menion, copying them to documentation as "info-box for geeks" probably makes the info easier to find while not irritating average users – what do you think?
Hopefully the RegEx feature will soon be re-used in search, because search works across folders and also inside descriptions, and in the other direction, the most recent used list of typed search terms becomes re-used in point filtering, because entering the special characters on a mobile with virtual keyboard is not really fun.
thanks you use and test this nice geeky feature :).
Your tips: maybe useful to @Michal Stupka who takes care of our manual?
- the difference in "Track filter" > you are correct. There was a tiny difference I've overlooked. Will be fixed in the next app version.
- not working regexes: I may suggest very nice page I use for testing: https://regex101.com .
- case insensivity > as far as I know, you can't define '/i' parameter for the regex as you do, but I need to do it directly in the code. I think it make sense to ignore case for such searches. So I'll hardcode ' Pattern.CASE_INSENSITIVE' flag to the next version.
Regex used also in point/track searches sounds interesting, good idea. I'll definitely think about it.
Jiří M. aka Menion
and which flavor - PCRE | Python | Golang | Java | .NET?
If you set "Java", it should work for sure, but it should make no difference in the syntax you will write I believe.
v4.11.0 came today to my device and my questions are solved: RegEx work in tracks, and RegEx are case-insensitive making them much more convenient. Thank you, Menion 🙂 BTW, regex101.com looks quite helpful at first glance!
Replies have been locked on this page!