SlickEdit Community

Archived Read Only Forums => SlickEdit 2017 v22 Beta Discussion => Topic started by: jporkkahtc on September 01, 2017, 06:37:44 pm

Title: find_next fail
Post by: jporkkahtc on September 01, 2017, 06:37:44 pm
find_next seems to get out of sync with the find options - in particular color coding.
I don't have repro steps, but basically I used big-find dialog to search for "blah", color coding: NotString,NotComment.

I hit FIND, and its good.
I hit F3, and the next thing it finds is "blah" as a string -- ignoring the color coding option.

As I tried to repro for writing this report, I've got the opposite problem - I've cleared the color coding options but they still seem to be being enforced by find_next.

I don't know if it matters, but I'm searching in a *.py file.


Title: Re: find_next fail
Post by: Clark on September 01, 2017, 11:13:31 pm
No luck reproducing this. Keep in mind that displaying the big-find dialog and changing color coding options has no effect until you do another find (press Find button). At least that's the way its supposed to work.