Search improvements (v1.5)

[FellippeHeitor]

In the latest development build, look for the following fixes/improvements:

• Updated help - new commands added (wiki updated too).
• Fixed search history list - it now properly shows even when the help is open and the list is too long (Thanks @Dav for reporting).
    [ You are not allowed to view this attachment ]  
• The "Find" button (yes, it's a button - a substitute for the F3 key to repeat the last search) now gets highlighted when hovered.
    [ You are not allowed to view this attachment ]  
• CTRL+F2 has been added as a shortcut to clicking the "back" arrow (quick navigation). Hi, @Cobalt!
• Dialogs Search->Find and Search->Change gained new functionality to allow ignoring text contained in comments (both REM and apostrophe comments) and in "strings". Conversely, you can also search for text exclusively inside "strings" or 'comments.
    [ You are not allowed to view this attachment ]  

If you are on the beta-testing wagon, please try to break the new features above and report below.

[Dav]

It's working well for me.  I'm testing the 32-bit version.  I've really been trying to abuse it, to find any bugs, but it's rock solid!   I found out an odd thing playing around - you can over-ride the IDE formatting settings, in code, by placing an underscore before the line.  Was surprised that the below code compiled as is.  Not that this matters for anything, but I just found it interesting that the IDE bypasses auto capping and formatting the code after an underscore.


1 _
do
a_
=_
rnd*3
_
for t=1to 43step 1
:_
_
print a,t+rnd*333
_
next
_
::::if inkey$<>""then end
_
loop


:)

Good job on what looks like will be another good version release!

- Dav

[FellippeHeitor]

Glad Search update is proving to be robust. Thanks for trying it, Dav!

And yes, the auto formatter doesn't mix with line continuation at all. If it's ever an issue, advice is to write the line first, so it gets formatted, and then break it with underscores if it's too long.