Users should certainly never see regex! That’s covered in User Interface Guidelines 101.
But surely you wouldn’t show them the LC wildcard filter either! $@%?$@%?$@%?$@%?$@%?$@%?$@%?$@%? Neville Smythe Director, International Go Federation VicePresident, Australian Go Association Inc. > On 3 Nov 2023, at 12:02 am, David Glasgow <dvglas...@gmail.com> wrote: > > > >> On 1 Nov 2023, at 11:24 pm, Neville Smythe <neville.smy...@optusnet.com.au> >> wrote: >> >> But I suspect you should allow for the required strings to be followed by >> punctuation or be at the end of the line, things which are hard to do with a >> simple LC wildcard search, at least in a single filter. > > > When I originally went down the wildcard route, I wrote some gentle text > preprocessing (using replace) to make sure words are always bounded by a > space, including before punctuation and at an eol. > > I also need users to see the reason the message appears in the results (i.e > the matched filter) so they are listed under a heading consisting of the > search term. Not sure what users would make of regex! > > Thanks again, > > Cheers > > David G _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
