Here's a nice little twist! This works if the arguements for itemOffset come from fields. it only breaks if you hard code them (or in my case pull the values from a database. I am willing to bet a nice steak dinner this is being caused by uniCode. The engine is probably expecting to search for unicode values and instead is finding UTF8 (or whatever it is).
Bob S > On Sep 7, 2016, at 13:59 , Bob Sneidar <bobsnei...@iotecdigital.com> wrote: > > Thanks Panagiotis. I will submit a bug report to that effect. Unfortunately I > need wholeMatches because contacttypes can be IT or SITES among other things > and replacing IT in contacttypes will result in SE instead of SITE. I am > working around it but this can bite someone in the arse hard if they are not > carefule. > > Bob S > > >> On Sep 7, 2016, at 11:10 , panagiotis merakos <merak...@gmail.com> wrote: >> >> It looks like "set the wholeMatches to true" is the culprit. Removing this >> line results in the expected behavior. >> >> On Wed, Sep 7, 2016 at 8:36 PM, Richard Gaskin <ambassa...@fourthworld.com> >> wrote: >> > > > _______________________________________________ > 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 _______________________________________________ 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
