QuickSearch eXtended

[Matthias030]

Hi. Thank you for this great tc addon.
Is it possible to search for files that have spaces in filename? If I enter a space in search field nothing happens.

[Samuel]

Yes it is.

Currently space is the and-separator-char.
If you search for: "cat dog" then you will find any file containing "cat" and "dog" in any order.

With the gui you may change the and-separator-char to anything you like, for example: "&" Then if you search for " cat & dog " you will find any file containing " cat " and " dog ". (with surrounding spaces)

[Matthias030]

This is what i was looking for.
Thank you!

[Samuel]

Your welcome.

[jjxu]

2Samuel
I wrote a file system plugin based on ScriptWFX, it read text file's contents and display them in tc's file panel, then we can filter out the contents we interest in, i use QuickSearch eXtended and find some problem:

1.I can't use "!@#$%^&*()_+~`-=|{}[]?><,./" these characters to filter in my plugin normally, on the contrary, tc's own quicksearch doesn't have this problem;
2.I can't set activate char and separator char to null in tcmatch.ini, as you know, i need to use some special character to filter "file contents" in tc's file panel in my plugin;

sorry i don't get previlege to post my plugin's download address.

Here is my tcmatch.ini content:
[general]
simple_search_activate_char=
regex_search_activate_char=
leven_search_activate_char=
preset_activate_char=~
simple_search_match_beginning_activate_char=
and_separator_char=" "
or_separator_char=~
wdx_separator_char=~
negate_char=~
case_sensitive=0
allow_empty_result=0
filter_files_and_folders=3
match_beginning=0
use_pinyin=1
srch_activate_char=
[wdx]
debug_output=1
wdx_cache=1000
[gui]
override_search=0
invert_result=0
one_line_gui=0
show_presets=0

[jjxu]

2Samuel
In my plugin(as i mention above), i need to filter out something like "pathto\file" when i type "path file", could you modify the option so that i can filter filename and it's path at the same time?

If possible, i hope QSX can filter "\", thank you!

[Samuel]

Could you please specify exactly what you want to do?

Here is what I understood:
1) Your Plugin reads the content of a whole file and returns its content.
2) You want to use your Plugin to filter files depending on their content.

a) You should use "~" (or some other unused char) for every unused activate/separator char. IIRC having more then one of "" will result in default values.
b) If I look into your "tcmatch.ini", you do not have it configured to use your plugin. See:
> "tcmatch.pdf" > 2. Features > content plugins
> "tcmatch.pdf" > 3. Customize > content plugins
> GUI > content plugins

By default you cannot filter for file paths. You have to use another content plugin for that.

Edit: I just read that you want to use it for WFX, instead of WDX.
Please post a link to the plugin. As you will loose "spam-bot" state with your third post.

IMO its better to filter by content with wdx. (and there already exist plugins)

[jjxu]

2Samuel,
thanks for your replying.
for example:
there are 3 lines in test.txt:
this is line 1, !@#$%^&*
this is line 2, ()_+~`-=|{}
this is line 3, []?><,./
in my FS plugin, test.txt will act as a directory, and there are 3 files in it:
this is line 1, !@#$%^&*
this is line 2, ()_+~`-=|{}
this is line 3, []?><,./
each line of test.txt's contents will be a file name in my FS plugin, then i can filter out "this is line 2, ()_+~`-=|{}"-this "file" by typing "2" in tc's file panel.
so, i may need filter "\" and other special characters(like "@#$") if it's in one line of test.txt.

[jjxu]

here is my plugin's dl address:
http://www.newsmth.net/bbscon.php?bid=837&id=44717

after install, upload a small text file to "\\\ScriptWFX\txtfilter\"

[Samuel]

I tried your plugin with the following tcmatch.ini

Code: Select all

[general]
simple_search_activate_char=
regex_search_activate_char=~
leven_search_activate_char=~
srch_activate_char=~
preset_activate_char=~
simple_search_match_beginning_activate_char=~
and_separator_char=" "
or_separator_char=~
wdx_separator_char=~
negate_char=~

case_sensitive=0
allow_empty_result=1
filter_files_and_folders=3
match_beginning=0
use_pinyin=0

And here are the results:
Only 3 chars are not working as expected: "*~\"

It's obvious that "~" doesn't work, because its the char for everything. (Just use another: for example "´")
I don't know exactly why "*" doesn't works. (I'm too lazy to look into it.)

"\" doesn't work because I handle the filenames with full path. (for example to filter files and folders)
I define the file name to begin after the last "\" (or the last "/"). So everything before "\" (including "\") is cut off.

I wont change something like this because many features depend on it and it will be much work. You could just replace "/" by "<s>" in your plugin. Afterwards search for "<s>".

You can also look into my sources. Feel free to build your custom version.

[jjxu]

thanks for your suggestion, i'll try it.

[icfu]

@Samuel:
The WDX functionality in your plugin is broken, am I the only one who has tried it out in the past months? Really weird...

The first added WDX plugin is saved as "wdx_text_plugin0" in tcmatch.ini, the second one as "wdx_text_plugin2". When the settings dialog is closed and called again, the WDX list is empty, obviously because you are trying to read wdx_text_plugin1 first...

This is wdx section after adding two plugins:

Code: Select all

[wdx]
debug_output=1
wdx_cache=1000
wdx_text_plugin0=Size@D:\TC\Plugins\WDX\DirSizeCalc\DirSizeCalc.wdx
wdx_groups=1,2
wdx_text_plugin2=Month (Creation Date)@D:\TC\Plugins\WDX\DateNames\DateNames.wdx

When wdx_text_plugin0 is changed to wdx_text_plugin1, the list is displayed in settings dialog and WDX starts working. Well, it works, but TC is getting slowed down massively whenever a quick search is done, not really usable.

Part of the problem seems to be that there is no delay after entering a char but the search kicks in instantly. So, when you try to enter "blabla", TC first searches for "b", then for "bl", then for "bla", etc..., or all at the same time, who knows, at least that's how the non-responsive GUI reacts.

There is another problem: The quick search popup is often split in two pieces, check this image...:
http://img51.imageshack.us/img51/3513/tcmatch.png

W7 Ultimate

[Samuel]

Version 2.0.1+ is available. (silent update)

2icfu
You are right about broken wdx. I fixed and uploaded a new version.

If you have some slow wdx plugins you should move them to the second wdx group: wdx_groups=|1,2 (also see gui)
Then you can access them by writing: "/text_in_wdx_plugin"

You may also increase wdx cache to more files to reduce the slowdown after first usage in big folders.

TC first searches for "b", then for "bl", then for "bla"

Yes this is a known problem. You may avoid it by using wdx groups and writing: "bla[pos1]/"

There is another problem: The quick search popup is often split in two pieces, check this image...:

Dont know what the problem could be. I use this AHK code for the position.

Code: Select all

WinGetPos,posX,posY,posDX,posDY,ahk_class TQUICKSEARCH
posX:=posX+posDX+5
gui,Show,X%posX% Y%posY% w183 h50 NoActivate

a) Do you have the problem with a clean wincmd.ini?
b) Do you use multiple screens?
c) Do you use multiple instances of TC
d) Do you use TC in an earlier version?
e) Do you use other programs in background?
f) Is it always the same position, or does it depend on other windows, TC movement, etc.
g) Could you reproduce it on another system?
h) Do you also get strange positions if you execute this ahk: "WinGetPos,posX,posY,posDX,posDY,ahk_class TQUICKSEARCH"

[tosbsas]

where did you upload - still says 2.01

[Samuel]

silent update

Didn't wanted to change urls, versions, etc.