tintoy / msbuild-project-tools-vscode

VS Code extension for MSBuild intellisense (including PackageReference completion).
MIT License
83 stars 17 forks source link

Please stop auto focussing the output window when I hover in a proj file #25

Closed NinoFloris closed 6 years ago

NinoFloris commented 6 years ago

Please stop auto focussing the output window when I hover in a proj file.

https://cl.ly/0N172K3Y0403

tintoy commented 6 years ago

Hi.

Sorry, it's not supposed to do that (I can imagine it'd be annoying); can you confirm that trace is false or not present in your VSCode settings?

"msbuildProjectTools": {
    "logging": {
        "trace": false
    }
}
NinoFloris commented 6 years ago

Thanks for your quick reply :)

Yes this is my config:

screen shot 2017-12-11 at 23 55 36

Works well otherwise though, great work!

tintoy commented 6 years ago

No worries - I think I see the problem :)

If I post a VSIX package here would you be willing to try it out and see if it fixes your problem?

NinoFloris commented 6 years ago

Sure no problem, I know how to by now ;)

tintoy commented 6 years ago

Ok, give me a sec - building one now.

tintoy commented 6 years ago

Ok - just unzip the VSIX and install into VS Code:

msbuild-project-tools-0.2.17.zip

NinoFloris commented 6 years ago

Still happens :/

Edit: Nvm had to remove the old one first, a weird vscode thing (as the new version number does show)

tintoy commented 6 years ago

Hmm, that's interesting - what version of VS Code are you working with? I've just tried it in both VS Code and VS Code Insiders and it no longer happens on either unless trace is set to true :-/

NinoFloris commented 6 years ago

Yep edited previous comment :) thanks for the help

tintoy commented 6 years ago

Phew! No problem - I'll create a proper release shortly, then you can install from the gallery (I think it'd automatically upgrade but I can't remember anymore if that's true).

tintoy commented 6 years ago

Ok, @NinoFloris - the new release is up in the marketplace. Pretty sure you won't have to upgrade the package by hand (since the extension Ids still match up) but if you find you're not seeing expected updates then you might need to just remove the extension and install it from the gallery.

Glad you like it, and sorry again for the annoyance :)

tintoy commented 6 years ago

(that's v0.2.17)