Request from Michael.
An obscure one I guess... when you define a hotkey (say Ctrl+F9) for an application Favorite it gets saved in the settings file against the application's EXE path. This makes sense, however if you have several favorites defined using the same EXE path - except that each have different command-line params - they automatically all get associated with the same hotkey.
For example I have defined several scheduled tasks in Windows, each with different command line params, e.g.:
C:\Windows\system32\schtasks.exe /run /TN "NoUAC\UAC Revo Uninstaller Pro"
As it stands I don't think QAP supports this approach (hotkeys against an EXE that has multiple matches but different params).
Granted, this one's a bit out of the ordinary, and QAP does work fine if you define these as menu popups alone (no shortkey).
Obscure but interesting one... Actually, favorite hotkeys are associated to "location", regardless of other settings (Advanced setting, Live Folder settings, etc.). This is a limitation of the current design.
The solution would be to associate hotkeys to a combination (concatenation) of the location and parameters (and maybe of other settings like "Start In" or "Live Folder" settings), for example:
Hotkey1=C:\Windows\system32\schtasks.exe /run /TN "NoUAC\UAC Revo Uninstaller Pro"|+^x
Hotkey2=C:\Windows\system32\schtasks.exe /run /TN "SomethingElse"|+^y
This may not be so hard. But backward compatibility may be an issue...