Can I block the QAP menu trigger (Middle Mouse Button) if it interfere with one of my other apps?

This page has been updated for Quick Access Popup v10.

Yes. There may be some applications where the user does not want the QAP menu mouse trigger (by default, Middle Mouse Button) to interfere with the app's normal behavior. QAP allows to block the QAP mouse menu based on the window title, window class or process name.

But, before considering blocking hotkeys, you could first see if another hotkey would best fit your needs. If yes, use the Options window, tab Popup Hotkeys to select different triggers for the QAP menu.

If you prefer the exclusion approach, open the Popup Menu tab in the Options. In the Exclusions list for Mouse trigger text zone, enter any part of the window title of the application to exclude (the window title is what appears in the top horizontal bar of the window). You can enter multiple exclusions, one per line.

 

For example, to exclude Google Chrome and Microsoft Word applications, enter the following two lines in the exclusion list:

Google Chrome
Microsoft Word

Click Save and try the to open the menu again in these windows. The menu won't show up. The QAP hotkey is disabled and the Middle Mouse Button click is sent to the target window as if QAP was not running.

Excluding dialog boxes

By default, QAP will only block the mouse hotkey in the app's main window. You can also disable the mouse hotkey in app's dialog boxes by adding the prefix * (asterisk) to the title or the class name, for example:

*3D Studio

In this example, the mouse hotkey will be blocked in both the 3D Studio Max main window and in its dialog boxes.

To be more specific

Using this technique, there may be situation where a window title in another app could include one of the exclusion strings you entered. For example, if you save a file in Notepad under the name "My Microsoft Word tips and tricks.txt", this window would be excluded because it includes the string "Microsoft Word". But you can be more specific with this:

- Microsoft Word

Adding the dash and space at the beginning of the string will exclude Word windows because the app name in the Word's title bar is always preceded by the document name and a dash between spaces.

To be a bit more technical

Another way to be more specific is to enter part of the app's "window class name". For example, Word's windows class name is "OpusApp" and Chrome' windows class name is "Chrome_WidgetWin". So, these two exclusion lines could be:

Chrome_WidgetWin
OpusApp

You can also exclude an application based on its process name. This is a solution for applications having variable class names. Usually, the process name is the file name of the application's executable file, for example the Chrome process name is "chrome.exe" and the Word process name is "winword.exe". So, the exclusions list could also be:

winword.exe
chrome.exe

How can I find a window class name, process name or a window title if the app has no title bar?

To identify the window you want to exclude, use the Get window info button at the bottom of the Exclusions list in the Options dialog box. It will prompt you to click in the target window with the QAP menu hotkey (Middle Mouse Button) and will copy the window title, class name and process name in your Clipboard. Paste this info in the exclusion list and edit it to remove unnecessary parts as described above.

 

There are other tools to gather more info about windows. I recommend this freeware utility: WinLister by NirSoft.

Please use the new QAP Support Forum to ask questions or post comments.

19 comments

  • Peter Huang

    Can I let the QAP menu trigger (middle mouse button) only works in Windows Explorer or in a file dialog box, and shift+middle mouse button works on any windows? (Just like how Folders Popup works)

    Thanks!

    • Hi Peter,

      No. QAP can launch favorites from any window. This is one of the thing users asked as I was adding different types of favorites to FP (applications, documents, links). But, as you read on this page, you can exclude windows or applications.

      This is the main shift for users migrating from FP to QAP. But you can get used to it quickly.

      • Peter Huang

        Below is my workaround to trigger QAP menu by middle mouse button only in Windows Explorer and file dialogue box. User needs to change QAP trigger button to ^Mbutton, and run the autohotkey script below:

        #IfWinActive, ahk_class CabinetWClass ahk_exe explorer.exe ; explorer
        MButton::
        SendLevel 1 ;
        sendinput, ^{MButton} ; set QuickAccessPopup to ctrl+MiddleButton
        return

        #IfWinActive, ahk_class #32770 ; file dialog
        MButton::
        SendLevel 1 ;
        sendinput, ^{MButton} ; set QuickAccessPopup to ctrl+MiddleButton
        return
        #IfWinActive

  • Tom

    The exclusion list does not work in 3D Studio Max, not even with Window Classes. Is there a solution?

    • Hi Tom,

      It is hard to tell because I do not use this app. Sometimes, apps user interface are build with various windows having different window title or class name. Also, some app windows can have different class name each time they are launched.

      Have you tried to enter only part of the window title or class name that would be common to various windows or would be permanent?

      Let us know.

      Jean

      • Tom

        I tried everything but now I just figured out that it are windows with the class name: #32770 that are not working.
        The Export Settings window in Adobe Media Encoder does not work and it has the same class number as the 3D Studio Max windows. But excluding that class name does not do anything...

        • Every standard Windows dialog boxes in any application has the class #32770. Exclusion list is for apps main window, to avoid the QAP hotkey (like middle mouse button) to interfere with the app. This interference should not occur in dialog boxes. This is why the exclusion is not applied there.

          Jean

          • Tom

            Why does it not work by their title then? Those windows aren't dialogue windows. But they're not main windows either.

        • But why do you want to exclude the QAP mouse hotkey in a dialog box? What is the issue?

          • Tom

            I don't want to exclude QAP in a dialogue box. But these screens that have a name but that general windows class are not dialogue boxes.
            For example, in 3ds max it's a curve editor for animation curves, in Adobe Media Encoder it's the preview window of the movie you're about to encode. In all these windows, middle mouse button is dragging the contents within around which we use a lot. So they're part of the software, but they're certainly not dialogue boxes. You don't choose folders or files in them. They're software screens...

            • Dialog boxes are not only for file operations (Open, Save As, etc.). Dialog boxes can be used for settings and a lot of tasks in a "child" window of the app's window. These windows (when built using windows standards) all have class name "#32770". There is no known way (I searched for it) to distinguish for sure file dialog boxes from other types of dialog boxes.

              This being said, what you would want is the QAP exclusion list to be check not only the current window name/class but also, if it current window is a dialog box, to this window's parent window.

              From what I see, this is feasible. Added to the wishlist:
              http://www.quickaccesspopup.com/exclude-dialog-boxes-based-on-name-or-class-of-parent-window/

  • george

    I'm having the same issues with the same software 🙂
    For a lot of these programs middle-mouse-button-hold-'n-drag means panning the viewport inside the window around, a bit like left-mouse-button-hold-'n-drag in Google maps. Anyway, if the parent thing would work that would be amazing!

    QAP saved me a loooooooooot of clicking already.
    Thank you again for developing it.

  • @Tom an dGeorge: I added this exclusion option in the current beta release (please see: http://www.quickaccesspopup.com/welcome-to-quick-access-popup-beta-test/).

    I updated the answer to this FAQ to reflect this change:

    By default, QAP will only block the mouse hotkey in the app's main window. If you want to disable the mouse hotkey also in the app's dialog boxes, prefix the title or class name with an asterisk, for example:
    *3D Studio

  • george

    Thank you for dealing with this so promptly.
    Would this also disable QAP in any "Open" or "Save as" windows opened by 3DSmax?

    Cheerio!

    • Tom

      I can confirm that it also disables it in the open/save windows.

      Maybe that could be made an exception when you have an * in your list that the open/save dialogue boxes keep their functionality?

      I thought maybe a work around would be to use an alternative hotkey for those programs (such as CRTL+CRTL) but that does not seem to work.

    • @George: My pleasure. All you have to do is to enter the correct exclusion criteria (title or class name) and put * before. See for more info:
      http://www.quickaccesspopup.com/can-i-block-the-qap-menu-hotkeys-if-they-interfere-with-one-of-my-other-apps/

      @Tom: Since the beginning of QAP, exclusion is used without including dialog boxes. For backward compatibility, I will keep the exception (*) for this recent change. About Ctrl+Ctrl (Options, second tab) and other keyboard hotkeys, they are not covered by the exclusion list.

      • Tom

        Unfortunately, that does not really solve my problem because I do want QAP to work on open/save/save as dialoague boxes. But as you said, this is probably not feasible due to the limitations of Windows.

        I'll stick with an alternative hotkey configuration. But many thanks for reacting so swiftly and for this great tool! Really saves me a ton of clicks!

        • Yes. Unfortunately, as I said, there is no safe way to distinguish open/save as dialog boxes from others.

          Thanks for reporting this issue.

Please use the new QAP Support Forum to ask questions or post comments.