Make Google Drive open DOpus instead of Explorer (recently synced files list)

I'm using Google Drive and if I click tray icon, there's a list of recently synced files. If I click one of them, its location is opened. The problem is the location is opened in Explorer, instead of DOpus.

DOpus integration with Windows works fine in almost all other applications I use (e.g. the same feature in Dropbox works as expected).

I do realize that this issue is probably more related to Google Drive than to DOpus but maybe you guys know a solution for this? I couldn't find anything interesting on Google.

This worked very recently at least.

What settings do you have on the Preferences / Launching Opus / Explorer Replacement page?

See attachment.
I tried all options but no luck.

Any feedback here? Does that even happen to other people too? I tried on my both computers and on both Drive tray popup opens Explorer. Any workaround for this?

I can verify it doesn't seem to work. Not sure why yet, it seems like they are using a non-standard method of opening the folder.

Ignore the above message, I realised I was trying on a dev machine that didn't have the Opus DLLs registered properly.

It does seem to work OK for me here. Maybe try reinstalling Opus over the top of itself (don't uninstall) as this should cause the DLLs to get reregistered. After a reboot you may find it's started working again.

Reinstalling didn't help.
Note that clicking on "Open Google Drive folder" opens DOpus as supposed. But clicking on a just synced file in the Drive tray menu opens Explorer. And it works this way on my both computers I use.

On both I use Windows 7 if that matters. For testing purposes, I installed Windows 10 on VirtualBox, tried with fresh install of DOpus and Google Drive and the result is the same. DOpus seems to be integrated properly as it replaces Explorer when opening Drive root folder, but clicking on recently synced files list opens Explorer.

Any other ideas?

Confirmed here. I don't think there is anything DOpus can do about it, as it seems that the Drive application directly calls Windows Explorer. Probably hard-coded stuff within the app. All companies have some engineers that are not up to the task. :slight_smile:

Ah sorry, that was the bit I missed. Yes, you're right. It seems like in that case they're running Explorer directly (using CreateProcess) rather than going through ShellExecute or SHOpenFolderAndSelectItems. Not much we can do to intercept that unfortunately (without a system-wide CreateProcess hook anyway, which would no doubt instantly trigger every anti-virus program on the planet).

You could always contact Google and ask them to change how they do it :wink: SHOpenFolderAndSelectItems is the proper API to use for that operation and Opus will intercept it automatically.

1 Like