FileSeek Discussions RSS

RE: Invalid number of lines

Keith Lammers — Thu, 16 May 2013 02:22:41 GMT

I think we're ok for now actually (DisplayFusion is the only other one, but it's already been translated). We'll definitely let you know if we need help with any others in the future.

Thanks again!

RE: Invalid number of lines

Capoeirista — Tue, 14 May 2013 22:05:32 GMT

Thanks you too. May need to be done a translation for others of a programs?

RE: Invalid number of lines

Keith Lammers — Tue, 14 May 2013 18:56:53 GMT

Will do, thanks for all of your hard work on the translations!

RE: FileSeek for Mac

Keith Lammers — Tue, 14 May 2013 14:48:54 GMT

There isn't currently a Mac version planned, but I've added your vote to the open feature request for one

Thanks!

FileSeek for Mac

Tushar Agarwal — Tue, 14 May 2013 07:25:59 GMT

Is there a version of FileSeek available for Mac OS ? If yes, where can I download it from ? If no, then are there any plans for developing one in the future ?

RE: Invalid number of lines

Capoeirista — Mon, 13 May 2013 21:06:17 GMT

Translation is ready, check.

RE: Invalid number of lines

Keith Lammers — Mon, 13 May 2013 20:34:36 GMT

I'll add that to our list, thanks!

RE: Invalid number of lines

Capoeirista — Mon, 13 May 2013 19:52:25 GMT

Now it is clear.

Can You increase the time display tooltip and show to the right of the cursor?
I think it would be more convenient for all.

RE: Invalid number of lines

Keith Lammers — Mon, 13 May 2013 19:00:09 GMT

This topic is fine

That option is to set how many lines will be shown in the preview pane after a result has been found. It only works when "Match query line by line" is enabled on the Advanced tab.

For example, if your file was like this:

Line 1
Line 2
Line 3
Line 4

And you've set the option to 1, then you query for "Line 2", it will show the following in the preview pane of the search results when you select the file:

Line 2
Line 3

Hope that makes sense!

RE: Invalid number of lines

Capoeirista — Mon, 13 May 2013 18:36:32 GMT

I also do not understand this function "Show this many lines after a search result:". What and where is it doing?

P.S. Or do I have to create a separate topic?

RE: Invalid number of lines

Capoeirista — Mon, 13 May 2013 18:17:46 GMT

Quote:
The lang file is actually newer, as we've changed some strings in it since FileSeek 3.0. Could you try updating to FileSeek 3.0.1 Beta 1 from the link below?

http://www.fileseek.ca/Download/Beta/

Thanks, now Everything is Ok.

Quote:

Also, I've moved the screenshots from your original post to our servers, as the image hosting site you linked to had some slightly inappropriate ads on it

RE: Invalid number of lines

Keith Lammers — Mon, 13 May 2013 18:04:02 GMT

The lang file is actually newer, as we've changed some strings in it since FileSeek 3.0. Could you try updating to FileSeek 3.0.1 Beta 1 from the link below?

http://www.fileseek.ca/Download/Beta/

Also, I've moved the screenshots from your original post to our servers, as the image hosting site you linked to had some slightly inappropriate ads on it

Invalid number of lines

Capoeirista — Sun, 12 May 2013 03:24:48 GMT

I have been translated into Russian, and when installed the trial version, began to translate the lang file. Then registered on the site in a group of translators and began to translate the website. When I downloaded the translation (from the site), and you add a folder and run the program it does not see it.
Then I compared the two files and saw that the file from the site there are lines that are not in my first translation.

For Example

Probably therefore I get an error when i run the program, if a file folder from the site

RE: another bug

Keith Lammers — Fri, 10 May 2013 17:05:26 GMT

Thanks Pete! I've found the issue, so we'll hopefully have it fixed up for the next beta.

RE: another bug

Pete Gomersall — Fri, 10 May 2013 16:42:48 GMT

See attached.
Note I have currently 10 machines setup with the registry code set in HKLM. I tend to run FileSeek as local administrator.
These all do same. These are all upgrades from 2 to 3 to this beta.

RE: another bug

Keith Lammers — Fri, 10 May 2013 16:39:52 GMT

Thanks Pete, I was actually looking for the export of the FileSeek settings in HKEY_CURRENT_USER

Could you send that over when you have a chance?

RE: another bug

Pete Gomersall — Fri, 10 May 2013 16:04:12 GMT

Keith,
See attachments.
Pete

RE: Feature Request - Lines before/after set for each search.

Keith Lammers — Fri, 10 May 2013 16:03:58 GMT

I'll put that on our feature request list as well. We'll need to investigate it some more, but we'll be sure to let you know if we're able to make that change as well.

Thanks!

RE: How to increase another "File Handler"？？

Keith Lammers — Fri, 10 May 2013 16:00:50 GMT

If the files that have a .RAW extension or no extension at all are just text files, you can just disable the "Process file contents using File Handers" option on the Advanced tab when doing your search. That will cause FileSeek to treat the files as plain text

Hope that helps!

RE: another bug

Keith Lammers — Fri, 10 May 2013 15:50:25 GMT

I haven't been able to reproduce this here, even with the license key in the HKLM\Software\Binary Fortress Software\FileSeek key.

Could you export your HKCU\Software\Binary Fortress Software\FileSeek key and attach it so that I can restore your settings on a test machine and try to reproduce this bug?

Thanks!

RE: Feature Request - Lines before/after set for each search.

David Gray — Fri, 10 May 2013 10:59:20 GMT

Great, thanks for implementing. Could I also request that these settings could be changed for each search, i.e. move them from the settings screen into the advanced search screen?

another bug

Pete Gomersall — Thu, 09 May 2013 23:07:50 GMT

Keith & Jon,
Every time I change a setting in Options I get the "thank you for registering" dialog - rather irritating. This was in 3.0. and still in b1. I have code in HKLM by the way.
Pete

RE: Feature request for path too long

Keith Lammers — Thu, 09 May 2013 20:17:18 GMT

FileSeek 3.0.1 Beta 1 is now available, and this should be fixed up. Please let me know if you still run into the same issue after updating!

Thanks!

RE: Preserve preview pane size

Keith Lammers — Thu, 09 May 2013 20:13:39 GMT

We've just released FileSeek 3.0.1 Beta 1 (http://www.fileseek.ca/Download/Beta), and this should be all fixed up.

Thanks!

RE: Feature Request - Lines before/after set for each search.

Keith Lammers — Thu, 09 May 2013 20:10:04 GMT

We've just released FileSeek 3.0.1 Beta 1 (http://www.fileseek.ca/Download/Beta) and the lines before/after are now independent settings

Thanks!

RE: How to increase another "File Handler"？？

Rick Hunter — Thu, 09 May 2013 17:27:43 GMT

Hello, my question is alike, How can I manage .RAW files or without extension files? Example "Filename"

Is there a way to make a file association with any program running on Windows or portable version? Example "Movie.dat" --> Open with... VLC Player ?

Or other option would be: Treat RAW files as TXT files (if can do so).

Thanks in advance

RE: FileSeek 3.0 hangs when the latest PDF iFilter 11.0.01 for x64 is used

Keith Lammers — Thu, 09 May 2013 15:17:06 GMT

No problem David!

RE: FileSeek 3.0 hangs when the latest PDF iFilter 11.0.01 for x64 is used

David — Wed, 08 May 2013 22:51:22 GMT

Thank you for taking care of this problem. Hope Adobe would fix it. Meanwhile, iFilter version 9 is still good to use.

RE: Match query to entire file (in other words)

Keith Lammers — Mon, 06 May 2013 19:23:24 GMT

The translation doesn't have to be an exact literal translation, so if there's a better phrase in Russian that describes the functions of those settings, definitely just put that in

If you have any questions about the functionality, just let me know!

RE: FileSeek 3.0 hangs when the latest PDF iFilter 11.0.01 for x64 is used

Keith Lammers — Mon, 06 May 2013 18:27:52 GMT

We've looked into this, and unfortunately there seems to be an issue with the Adobe PDF iFilters v10 and higher. We couldn't get them to load, no matter what we tried, and we also found this: http://forums.adobe.com/thread/927535

Looks like the best option would be to stick with the Adobe PDF iFilter v9.

Thanks!

RE: FileSeek 3.0 hangs when the latest PDF iFilter 11.0.01 for x64 is used

Keith Lammers — Fri, 03 May 2013 19:48:05 GMT

Thanks for letting us know about this issue! I was able to reproduce it here, and we'll investigate whether it's something we can fix, or if it's just a bug in the iFilter that's out of our control.

Thanks again!

RE: Feature request for path too long

Keith Lammers — Fri, 03 May 2013 17:10:19 GMT

Thanks Pete! I was able to reproduce this here using your instructions, although it seems to be an intermittent issue for sure. We're looking into it and we'll hopefully find a solution to it soon

Match query to entire file (in other words)

Capoeirista — Fri, 03 May 2013 02:36:23 GMT

I'm doing a translation into Russian. The function is clear to me, but I can not find the right words to translate. Specifically, the word "Match".

P.S. Also for "Match query to each line in file".

Help me?

RE: Confusing cart

Keith Lammers — Thu, 02 May 2013 20:29:02 GMT

Thanks for the feedback, it's much appreciated! We'll certainly review the purchasing process to see if it can be improved.

Thanks again!

RE: Index Option

Keith Lammers — Thu, 02 May 2013 20:27:02 GMT

Glad to hear you like FileSeek! I'll certainly add this to our feature request list, and if we're able to implement it in a future version, we'll be sure to let you know

Thanks!

RE: Feature request for path too long

Pete Gomersall — Thu, 02 May 2013 14:51:35 GMT

C:\Temp\test
A - folder name in query
1) Use Delimon to create long path
2) Pick a folder name on Delimon path within standard 260 character limit
3) Search for folder name with only folder names checked returns folder name AND files in that folder (they have foldername as prefix)
4) Click on returned folder name and choose delete. FileSeek deletes all files in this folder and all sub folders but does not remove any folders
B - folder name in include file
Same process same result

Now in all tests I can't delete the returned folder in FileSeek even when I restart the application and it only returns that single item

RE: Feature request for path too long

Keith Lammers — Thu, 02 May 2013 13:40:27 GMT

Ok, couple more questions:

Did you have any searches running in other tabs?
Were you searching using query text with match files/folders enabled, or just using the Include Files box?

Confusing cart

g00p3k — Thu, 02 May 2013 12:04:20 GMT

I know of at least one sale lost because the "shopping" cart was confusing. I'd seriously recommend you have a single Binary Fortress page, with the individual products, as the individual pages for each product is really confusing, as well as makes it less likely someone would purchase the entire package of programs you offer.

my 10 cents, as I'm a fan. Thanks!

Index Option

g00p3k — Thu, 02 May 2013 12:03:00 GMT

I really enjoy supporting your software and appreciate the hard work. I'd like to ask that you consider adding an option for saving a small index for chosen folders. Make it optional. I have thousands of code files to search and searching through .sql files seems to take a while, it would be awesome if some indexing options were available for people who use it for full text searches. Having the chance to have near instant results would be perfect!

I know its a big request, but maybe consider it for the future. I'll still be a fan no matter what

FileSeek 3.0 hangs when the latest PDF iFilter 11.0.01 for x64 is used

David — Thu, 02 May 2013 03:15:47 GMT

Hi,

I use Windows 7 Home Premium x64 SP1 and Adobe Reader XI 11.0.02.

I don't use the "Windows Search" service, and disabled it since day 1.

The version of FileSeek (free) that I'm using is 3.0. I have also used PDF iFilter 9 for x64 until the day before yesterday. With that iFilter, I had no problem.

Yesterday I un-installed iFilter 9 and installed the latest 11.0.01 version. After that, FileSeek crashed whenever it searched the contents of a PDF file. So, I un-installed the 11.0.01 version and re-installed the 9 version. And FileSeek works well again.

But I suspect it maybe the newer 11.0.01 iFilter that causes the problem because when it's installed, Windows Explorer can not search PDF files, either. From the search box in the upper righthand corner of the Windows Explorer dialog, I tried to search for some words that I knew were contained in some PDF files, constructing my search phrase with the content:<key word> format. But Windows Explorer did not return any matched file.

Does anybody encounter the same problem with the new 11.0.01 iFilter?

RE: Feature request for path too long

Pete Gomersall — Tue, 30 Apr 2013 20:14:02 GMT

Search was completed

RE: Preserve preview pane size

Keith Lammers — Tue, 30 Apr 2013 19:46:14 GMT

Thanks for letting us know about this! I've added it to our list and we'll post an update when we're able to get it fixed up

RE: Feature Request - Lines before/after set for each search.

Keith Lammers — Tue, 30 Apr 2013 19:44:23 GMT

Thanks, glad to hear you like FileSeek! I've added this to our feature request list, and we'll be sure to post an update if/when we're able to implement it.

RE: Feature request for path too long

Keith Lammers — Tue, 30 Apr 2013 17:21:11 GMT

Quick question. Was your search still running, or paused while you were trying to delete the file?

RE: Feature request for path too long

Keith Lammers — Tue, 30 Apr 2013 17:16:58 GMT

Interesting! We'll test this out here and try to reproduce it.

Preserve preview pane size

g00p3k — Tue, 30 Apr 2013 14:21:37 GMT

Bug report,won't preserve preview pane size.

Feature Request - Lines before/after set for each search.

David Gray — Tue, 30 Apr 2013 09:23:53 GMT

Hi,
I would like to request that it is possible to chose the number of lines to show before and after the result independently, i.e. in the advanced search options. At present it seems I can only set these globally in the options and have to have the same number of lines before/after.

Great software btw!

RE: Feature request for path too long

Pete Gomersall — Fri, 26 Apr 2013 20:59:20 GMT

Keith and Jon,
I have just spent half and hour testing the long path feature. The querying works fine and FileSeek will error on long paths if it finds one if the appropriate check box is selected. It will also enumerate correctly if you use a query for a file\folder at the end of long path without the check box.

However, FileSeek is really inconsistent about deleting folders on long paths that may contain subfolders and files. I cannot find any rational. It will not delete either via a right click > delete or highlight and press delete and then some time later it will delete. This is what was happening earlier in the week when I was testing.

OK - I believe I have found what happens. If I now close and reopen FileSeek I can then delete a higher folder on the long path if I just specify that folder as a query.
I suspect if I do a query and FileSeek returns long path and then you try to delete somewhere I believe there is a handle open within FileSeek and it will not delete. Maybe you need to test some more - and provide some deletion error logic?

For reference I was using Delimon to create the paths. Then I made sure nothing else had handle anywhere on the path.

Pete

RE: Feature request for path too long

Pete Gomersall — Fri, 26 Apr 2013 20:23:12 GMT

Keith I think I found it - "Show an error and skip path when longer than 260 characters"

RE: Feature request for path too long

Pete Gomersall — Fri, 26 Apr 2013 20:16:41 GMT

Keith,
I see you released v3 and it handles paths that are too long. However - what was decided about my last question? I don't see anything obvious that is included.
Pete