Showing the Windows Explorer Context Menu in Eclipse
Under development, basic context menu handling is working. The explorer context menu items can be added to the Eclipcse context menu in different ways:
- The whole explorer context menu is shown as submenu "Explorer" in the Elipse context menu
- Only specific entries are added to the Eclipse context menu where the following tools are supported:
- Beyond Compare
- Open With...
The follwoing context menu entries are currently not supported (not sure why they are not working, looks like the can only be executed directly from the Windows Explorer):
- Sharing (Entry "Share")
- Modern Sharing (Entry "Give acces to")
The screenshots below show example context menus based on the described configuration.
ContextQuickie2 requires an installed Microsoft Visual C++ Redistributeable package which can be downloaded here.
The release versions are available at the Eclipse Marketplace
Alternatively, you can use the following update sites when installing new software in eclipse:
- Releases: http://rolandomagico.github.io/ContextQuickie2/Releases
- Development: http://rolandomagico.github.io/ContextQuickie2/Development
The behavior can be configured in the workspaces preferences:
Menu Entry "Open"
The menu entry "Open" is implemented to open the selected files/folders with the Windows Explorer.
Because there are context menu extensions which don't support synchronous invocation, the progress reporting to Eclipse is done by monitoring the child processes of Eclipse during invocation. If there is a new child process which is known to ContextQuickie2 after invoking a context menu command, the progress of the command execution can be monitored in Eclipse. If there isn't a new child process after invoking or a command or the process is unknown to ContextQuickie2, progress monitoring cannot be done.
Currently, the following processes are known to ContextQuickie2:
- Bcompare.exe for Beyond Compare
- TortoiseGitProc.exe for TortoiseGit
- TortoiseProc.exe for TortoiseSVN
- thgw.exe for TortoiseHg
The described behavior also affects refreshing the workspace after a command was executed. As an alternative, you can enable "Refresh using native hooks or polling" in the workspace preferendes to let Eclipse update your workspace independent of ContextQuickie2.