LookingFor: A Masm64 tool to find strings in files.

[HSE]

Hi all!

I have some ideas about mask for file inclusion and exclusion, but finally don't have much sense 

Then I made just very standard: now  is available " * " for all files to search, " *. " for files without extension and for only extension files " .* " was already working.

Update in first post.

Regards, HSE.

[six_L]

Hi,HSE
Great! Looking for some files at attosecond.

Regard.

[greenozon]

If I set dir to say
c:\ddd
(the dir is real and has files in it)

and pressing "Find" button
I"m hitting strange error: (which repeats 2 times in a row)

---------------------------
LookingFor
---------------------------
Fail to set directory
---------------------------
OK   
---------------------------

also even after error the Cancel button is still actual


2) If I apppend \ to the dir like
C:\ddd\
then tehre is another error

---------------------------
LookingFor
---------------------------
Name or extension target problem
---------------------------
OK   
---------------------------


and button returns immediately to Find

3) if set c:\ddd* then app eats 100% CPU and doing nothing

[HSE]

Hi six_L!

Great! Looking for some files at attosecond.

Thanks.

Regards, HSE

[HSE]

Hi greenozon!

The target must have a path and a file mask. Perhaps it's no so clear in the help 

c:\ddd
(the dir is real and has files in it)

and pressing "Find" button
I"m hitting strange error: (which repeats 2 times in a row)

---------------------------
LookingFor
---------------------------
Fail to set directory
---------------------------
OK 
---------------------------

also even after error the Cancel button is still actual

In this case you are searching "c:\" as path and "ddd" as mask. Because it's searching entire C: disk, is failing to access some long path or unicode name directory. 

After message, it skip that directory and search reasume (I think).

3) if set c:\ddd* then app eats 100% CPU and doing nothing

In this case you are searching "c:\" as path and "ddd*" as mask. Probably it's the same that case 1 but, because wildcard, check the mask it's slower (again I think). I will test these cases.

The correct target for this search could be:

Code Select Expand

c:\ddd\*

2) If I apppend \ to the dir like
C:\ddd\
then tehre is another error

---------------------------
LookingFor
---------------------------
Name or extension target problem
---------------------------
OK 
---------------------------
and button returns immediately to Find

That it's correct because there is no mask. Perhaps error message need to be a little more verbose 

Thanks very much, HSE

[HSE]

Hi all!

Some error messages a bit more descriptive, and now catch some error to access target path.

Update in first post.

Regards, HSE.

[greenozon]

Thanks a lot for the fresh build!
new err boxes are much better, but.. found out this one -

---------------------------
LookingFor:
---------------------------
Could not open
---------------------------
OK   
---------------------------

it happens when fill in very long value in the 1st drop down
also it's tricky to show this err...
try to click and on Find by mouse -> nothing
press Space -> gotcha

[HSE]

Hi greenozon!

---------------------------
LookingFor:
---------------------------
Could not open
---------------------------
OK 
---------------------------

That could be an error or not, but anyway a good point 

That message popup after click in some filename that match definitions.

You can see how that work in procedure ListProc, inside more.inc file.

If file extension is .bat or .CMD, shell call \masm64\qeditor. That is hardcoded but you can change path or editor and rebuild program. This necessary to prevent file execution.

Perhaps that also happen with other extensions associated with a program not present or moved.

Because is a tool for programming, is expected that extensions of interest have associated an editor.

try to click and on Find by mouse -> nothing
press Space -> gotcha

There are remains from early development 

Thanks, HSE.

[HSE]

I all!

I failed to reproduce greenozon problem

Anyway now editor for *.bat, *.cmd, and *.js is not longer hardcoded.

Clicking with mouse or pressing Enter key will open selected file in result list. Because is a tool for programming, is expected that extensions of interest have associated an editor.
   
   Executable files will not open to prevent unwanted runnings.
   
   In similar way *.bat, *.cmd and *.js files will not run. But in this cases they will open in an editor. By default /masm64/qeditor is that editor. But is possible to select a new path or editor. If default or stored editor fail, a dialog will ask a new path or editor. Later, editor could be changed in LookingFor.ini file.

Update in first post.

Regards, HSE.

[HSE]

Minor update to help file (in first post). Now Release 1.0