QAP can read the current Windows folders custom icons and even set new custom icons to Windows folders .
When you create a favorite folder, if the folder already has a custom icon (configured in the hidden system file desktop.ini), this icon will automatically be associated to your new favorite and shown in your QAP menu.
If the folder has no icon, you can use the Add/Edit favorite dialog box link Set Windows folder icon to change the icon in the folder's desktop.ini files to the image selected for your favorite. That way, your QAP menu and your Windows file system will show the same icons for your favorite folders. QAP can also Remove Windows folder icon if you want to revert your changes.
See this YouTube video!
Users running QAP on Windows Server, please read the note at the end of this entry.
The Recent folders menu lists the recent places memorized by Windows. An option in the General tab of the Options window determines the number of recent folders displayed in the menu (default is 10).
Quick Access Popup Recent folders are taken from the Windows virtual folder Recent items (C:Users[username]AppDataRoamingMicrosoftWindowsRecent or, using the appdata variable, %appdata%MicrosoftWindowsRecent).
This Windows system folder lists the files and folders recently accessed by the user. Windows is using this list to populate the Recent Places virtual folder found in Explorer left pane. Recent Places is a subset of the Recent Items, showing only folders. Recent items are also used to populate the applications Jump Lists.
The Recent folders menu is a subset of the recent places memorized by Windows. You can reset the whole list of recent items:
- Open this folder:
or use this shortcut:
- Make sure the navigation pane is visible. If required, use the Organize menu.
- Right-click the Recent places in the navigation pane and select Clear Recent Items List. Recent items are now gone and Recent Folders menu in Quick Access Popup is now empty.
In some setup, the QAP context menus may work in Windows Explorer windows but not in a custom file manager (like Total Commander). Or the opposite.
This is generally because some applicatinos are running with different access privileges.
For example, if your file manager is running with administrator permissions while QAPmessenger.exe (that app transmitting commands from context menus to QAP) is running with standard permissions, messages sent from the context menu could not be received by QAPmessenger. Maybe you should run your file manager with regular permission or, on the opposite, launch QAPmessenger.exe with elevated privileges.
The opposite could also be true: if QAP runs in admin mode and Windows Explorer (or Total Commander) in standard mode, context menus in Explorer could not launch QAP commands because QAP has higher permissions than Explorer. Context menu can only call apps having privileges equal or lower than Windows Explorer has.
Please read more about QAP and Windows Access Control List (ACL).
To find more about installation and enabling of Explorer context menu, read the Explorer Context Menus Help.
Note to power users with more technical knowledge about ACL: do not hesitate to use the comment form below to give more detailed or accurate information.
Most of the time, this issue is related to ACL (Windows Access Control List).
Each window in Windows is launched with a given set of rights. Basically, there are two levels:
- user level (standard permissions)
- administrator level (elevated permissions)
With elevated privileges, user can make changes to the system that can affect all other users on the system.
Quick Access Popup hotkeys (by default, middle mouse button) only work on windows that have equal or lower access level. If you start an application with an higher "administrator" privileges (using the Run As Administrator Windows Explorer menu), QAP will not have the permission to open its menu over the windows created by this app. To do so, you would have to also launch QAP with administrator privileges.
Is it a good idea to launch QAP as Administrator? You have to know that every program started from QAP will the also inherit these enhanced rights. This could allow them to do changes on your system without prompting you. From a system security point of view, this may put your system at risk. In other words, you have to know what you are doing.
Yes. Quick Access Popup supports regular file system folders and UNC locations like network folders or WebDAV folders (Sharepoint libraries, etc.).
HTTP locations (URL format) will be automaticaly transformed to network path (UNC format) for compatibility with Windows Explorer. For example, http://abc.server.com/folder/subfolder/My Name.doc will be replaced by \abc.server.comfoldersubfolderMy%20Name.doc
In a file Explorer, if a location is password protected, you may need to be logged in manually *before* navigating to it using Quick Access Popup.
Yes. Tech support, sysadmin and other power users love it!
In any file path (folder, document or application), the system environment variables like %appdata%, %public%, %temp% or %userprofile% (etc.) are supported in favorite location (for example: "%appdata%MicrosoftTemplates" will take you to the folder "C:Users[username]AppDataRoamingMicrosoftTemplates").
System variables can also be inserted in favorite advanced settings Parameters, Launch with this application and Start in. See What are favorites advanced settings?
You can also enter a location without path. In this case, the file is searched in the PATH environment variable directories or in app paths in the Windows registry. In these examples, the folders in the resolved path column are assumed to be in the PATH variable. If you enter an application location without a file extension, it is searched for all executable extensions in the PATHEXT variable: .COM; .EXE; .BAT; .CMD; .VBS; etc.
|File without path
Yes.You can enter path such using the ".." (parent directory) and "" (root directory) symbols in favorite locations or advanced settings. Relative paths are "expanded" based on the current QAP working directory (see What's the QAP working directory?). In the following table, the relative paths are expanded as if the working directory was "M:MyToolsQAP".
That way, a user having to run various tools on a host PC can carry a set of apps on a USB drive or key and use Quick Access Popup to easily launch his tools regardless of the drive letter assigned to the USB device by the host system. Combined with the use of system environment variables and special folders to easily access host PC's system folders and user's data, this make QAP the perfect tool for tech support users.
Relative paths can be used in favorite locations, advanced settings Parameters, Launch with this application and Start in. It can also be used for icons with the Edit icon resource link in the Menu Options tab of the Add/Edit favorite dialog box.
You can also enter a location without path. In this case, the file is searched in the PATH environment variable directories or in app paths in the Windows registry. In these examples, the folders in the resolved path column are assumed to be in the PATH variable. If you enter a location without a file extension, it is searched with all executable extensions in the PATHEXT variable: .COM; .EXE; .BAT; .CMD; .VBS; etc.
|File without path
The working directory is the folder where the QAP settings file QuickAccessPopup.ini is saved and updated.
If you installed QAP using the "one-step installation" procedure, the working directory is [user folder]AppDataRoamingQuick Access Popup (for example, C:UsersJeanAppDataRoamingQuick Access Popup).
If you preferred the portable installation, by default the working directory is where the QuickAccessPopup.exe program is running.
In any case, you can set your own working directory by editing the QAP shortcut in the Startup folder (or create your own shortcut) and set the working directory in the Start in: field of the shortcut.
This is probably because you are using QAP on an HDPI-devices (like Surface Book). On these screens, icons on QAP Settings window may not scale properly. See this example: on the left, the Settings window on a standard desktop PC and, on the right, the same window on a Surface Book.
The scaling effect also impacts icon sizes in QAP popup menu. You could compensate this scaling by changing menu icons size in Options but this would not fix the buttons icon size in the Settings window.
Thanks to QAP user Jörg Giencke, you can use this tip from brianapps (the developer of Sizer 4.0): right-click the Quick Access Popup executable icon in Windows Explorer, select Properties, then Comptability, check Override high DPI scaling behavior and select System from the dropdown list. This goes for Windows 10 Creators Update (and other Windows 10 version on HDPI-devices?). After that everything displays just fine on Surface and other HDPI devices.