Edge case for Zeal on Windows

[szhongren]

When calling the extension from within VS Code and it's the first time starting Zeal after a fresh start of Windows, the same problem that was fixed with the start dash-plugin:// && ... occurs again. Not really sure how to go about dealing with this, but I'll start trying to figure it out. I think it's something on Zeal's end.

[szhongren]

Fix is coming with next release of Zeal. Also handles the start dash-plugin:// && start stuff. Turned out to be a Qt bug.

[deerawan]

@szhongren cool 👍

[xuzeshen]

1. environment：win10, zeal 0.4.0(current latest), vscode 1.17.2
2. error: start dash-plugin:// “can't find application”

[eamigo86]

@Darcy-FzR, I have same error !!!!

[szhongren]

@Darcy-FzR @eamigo86 what happens when you try running start dash-plugin:// on the command line?

[szhongren]

I just upgraded and got it too, it seems to be a change in how zeal is installed, it's not registering zeal as a handler for the dash-plugin URI. I'll take a look

[szhongren]

@Darcy-FzR @eamigo86 go to where your zeal executable is installed and run ./zeal --register

[szhongren]

I can add some code to automatically register the URI handlers in this extension, but it's going to be fragile unless we have a new setting to specify the Zeal install location, so I'm not going to for now