AutoHotkey Community

Say you have an MDI application which behaves well when the file open dialog is used and badly (opens a new window) when you start it a second time with a file argument. (The latter, of course, is what usually happens if it is the default app for the file type and you open a document in a file manager.)

The following hack fixes this behavior by simulating file open dialog input:



Things to customize according to your needs:

• window title patterns (WinExist parameters)
• command-line to run the app
• maybe the key stroke CTRL+o to open the dialog
• maybe the pause after CTRL+o

You can then set up a file association with autohotkey.exe "AHK_script" "%1" as mentioned in the code.

I've obfuscated the application name a little since i'm not sure whether its license permits this. Maybe someone is brave enough to post a guess so that this topic can be found easier.

I too hate the multiple instance of pdf readers when files are opened from an explorer window.



Are all the " to be used literally in the file association? I tried a couple of combinations but no cigar

Passing Command Line Parameters to a Script





The %1 (should be %1%) is the variable containing the first "input", make sure you feed it something

maybe I am a little slow, even with the "%1%", I go to Tools>Folder Options>File Types and Click the Change Button, then Browse and enter the full path ie C:\Program Files\AutoHotkey\AutoHotkey.exe" "c:\myfolder\myfile.ahk" "%1%" Directly into the file name box.

I get the error:

* Windows:

1. Explorer menu: Tools -> Folder Options -> File Types
2. Select file type, press "Advanced"
3. Select "Open" and press "Edit"
4. Insert your command line into the field "Application used to perform action"

Windows uses %1 (%2, %3 etcet.) to denote the dropped/activated file-path(s) as variable(s).

If a command line contains paths with spaces, they need to be enclosed in double-quotes.

Replace everything including the <> in the following examples with your values:



* AutoHotkey:

Passing Command Line Parameters to a Script, the Run command

AutoHotkey uses %1% (%2%, %3% etcet.) to denote the dropped/activated file-path(s) as variable(s).

If a command line contains paths with spaces, they are preferred to be enclosed in double-quotes (but it is not always necessary). Don't forget to escape the comma's.

---

So, when in Windows:



try this instead



or this



if you compile your pdfopener script, you could use:



HTH

Thanks n-l-i-d.

I did as you said except I had to convert the script into an exe for it to be accepted - maybe because my ahk association is not registered correctly?

The advanced button was not available at first because I had a custom association already - running pdf 5 and reader 8 on same machine.

I made a few adjustments to the script, using sendinput and winwait - in preference to send and sleep - so far so good.

Sorry for the late reply - i've been on vacation. Now all which is left to be answered is

The ahk association shouldn't matter here. With the correct *.pdf association Windows knows that it should start Autohotkey with the AHK script and file arg, and Autohotkey knows what to do with that regardless of the *.ahk association.

We use an old version of acrobat at work, but it still supports most of the pdfs I receive. Just resurrected this after IT deployed a new one that is not as good for reviewing and rotating drawings.

...lol...I actually have the opposite problem...& I would reverse your "well" & "badly" terms, I consider it bad to open in an existing window...I don't like window-cannibals.

Acrobat will always open PDFs in the "same window" or "same process"...I want all my PDFs in their own window & own process, for which I need to used Acrobats /n command line param.

But I do agree that ALL programs need...

• a default in Preferences for what to do (new window/tab/process)
• a command line param for new window/process always
• a command line param to open in an existing window, if possible