topbanner_forum
  *

avatar image

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  • Thursday March 28, 2024, 7:41 pm
  • Proudly celebrating 15+ years online.
  • Donate now to become a lifetime supporting member of the site and get a non-expiring license key for all of our programs.
  • donate

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - JohnJ [ switch to compact view ]

Pages: [1]
1
Find And Run Robot / Folder Modifier Bug?
« on: July 16, 2014, 03:46 PM »
There appears to be a bug in launching certain filetypes using an alias (in this case files with an '.ahk' extension) when a folder modifier is used instead of the direct file path in the result box. Here is a simple example that fails for autohotkey '.ahk' files:

I create two simple alias: the first uses the autohotkey path directly and the second uses a defined folder modifier 'ahk' that has that same path

1. alias: 'ahk1'
    regex: ^ahk1 (.*)$
    result box: ahk1 $$1 | dosearch c:\autohotkey\ $$1

2. alias: 'ahk2'
    regex: ^ahk2 (.*)$
    result box: ahk2 $$1 | dosearch +ahk $$1
The folder modifier 'ahk' is defined simply as the same directory used in 1) above: i.e., an ahk modifier definition for directory: c:\autohotkey

When I use the above formats for normal files, e.g., .exe, .lnk etc. the above two formats perform identically and work correctly. But for the above ahk example case 2, the search acts normally and finds the correct file and that file will launch correctly if I launch it from the context menu. But if I hit enter or try to double click on the found result a new search simply occurs and i only see 'Searching c:\ ...' and the file does not launch. This only happens in the case of the .ahk extension. All normal extensions work perfectly. I tried every possible launch option and the error still occurred.

It appears that in the case of an unrecognized extension (here 'ahk') the launch routine, only when a modifier is used, gets confused with that unrecognized extension. I am using x64 Win 8.1 and have associated the .ahk extension with autohotkey and, as I said above, the launch works fine as long as I use the path itself in the alias result box instead of the folder modifier +ahk.

I also tried creating a separate folder and add shortcuts (.lnk) to the '.ahk' files and then tried version 2 above using a modifier; those shortcuts worked fine. There was no problem with FARR recognizing the .lnk file to the .ahk file and then correctly launching the .ahk file when I used a folder modifier to that lnk directory.

For the time being I am simply using that second .lnk directory to launch .ahk files. Incidentally, this appears to be a good technique to quickly create multiple 'alias' names for a single file since the shortcuts can each be differently named. If you create a new folder modifier to that shortcut folder, those new alternate file ('alias') shortcuts can then be used to access the same file using multiple aliases ... very convenient!.

Pages: [1]