Thanks Mark, I think it's the same bug, except on OSX. I'm using the linestoskip parameter of lineOffset as you were. I'm using lineOffset in a loop to return lines between a start and end line number. I've worked around the problem by deleting the lines after I've finished using them, so the start line number is always 1. For some reason it manages to get the correct offset for the end line number that way.
Pete lcSQL Software <http://www.lcsql.com> Home of lcStackBrowser <http://www.lcsql.com/lcstackbrowser.html> and SQLiteAdmin <http://www.lcsql.com/sqliteadmin.html> On Wed, Oct 14, 2015 at 4:28 PM, Mark Talluto <[email protected]> wrote: > > On Oct 14, 2015, at 4:05 PM, Peter Haworth <[email protected]> wrote: > > > > Has anyone run into problems using lineOffset in LC8? I'm seeing it > return > > an incorrect line number in some cases. > > > > I'm wondering if it could have something to do with the data I'm > searching, > > since some lines have the characters \n embedded in them > > > > > It may be related to bug: http://quality.runrev.com/show_bug.cgi?id=15512 > <http://quality.runrev.com/show_bug.cgi?id=15512> > > > Best regards, > > Mark Talluto > canelasoftware.com <http://canelasoftware.com/> > CassiaDB: The rapid development, free local storage database, made for > LiveCode developers: livecloud.io <http://www.livecloud.io/> > > > > > > _______________________________________________ > use-livecode mailing list > [email protected] > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
