ricksladkey / smoothscroll Goto Github PK

Install log:

2020-01-29 06:35:45 - Microsoft VSIX Installer
2020-01-29 06:35:45 - -------------------------------------------
2020-01-29 06:35:46 - Initializing Install...
2020-01-29 06:35:46 - Extension Details...
2020-01-29 06:35:46 - 	Identifier      : 9ec8f525-55cf-419a-b3df-1436deadbeef
2020-01-29 06:35:46 - 	Name            : Smooth Scroll
2020-01-29 06:35:46 - 	Author          : Rick Sladkey
2020-01-29 06:35:46 - 	Version         : 2.0.2
2020-01-29 06:35:46 - 	Description     : Smooth scrolling for the Visual Studio text editor
2020-01-29 06:35:46 - 	Locale          : en-US
2020-01-29 06:35:46 - 	MoreInfoURL     : https://github.com/ricksladkey/SmoothScroll
2020-01-29 06:35:46 - 	InstalledByMSI  : False
2020-01-29 06:35:46 - 	SupportedFrameworkVersionRange : [0.0,2147483647.2147483647]
2020-01-29 06:35:46 - 
2020-01-29 06:35:46 - 	Supported Products : 
2020-01-29 06:35:46 - 		Microsoft.VisualStudio.Community
2020-01-29 06:35:46 - 			Version : [11.0,17.0)
2020-01-29 06:35:46 - 		Microsoft.VisualStudio.IntegratedShell
2020-01-29 06:35:46 - 			Version : [11.0,17.0)
2020-01-29 06:35:46 - 		Microsoft.VisualStudio.Pro
2020-01-29 06:35:46 - 			Version : [11.0,17.0)
2020-01-29 06:35:46 - 		Microsoft.VisualStudio.Enterprise
2020-01-29 06:35:46 - 			Version : [11.0,17.0)
2020-01-29 06:35:46 - 		AtmelStudio
2020-01-29 06:35:46 - 			Version : [7.0]
2020-01-29 06:35:46 - 
2020-01-29 06:35:46 - 	References      : 
2020-01-29 06:35:46 - 
2020-01-29 06:35:46 - Searching for applicable products...
2020-01-29 06:35:46 - Found installed product - Global Location
2020-01-29 06:35:46 - Found installed product - ssms
2020-01-29 06:35:46 - VSIXInstaller.NoApplicableSKUsException: This extension is not installable on any currently installed products.
   at VSIXInstaller.App.InitializeInstall(Boolean isRepairSupported)
   at VSIXInstaller.App.InitializeInstall()
   at System.Threading.Tasks.Task.InnerInvoke()
   at System.Threading.Tasks.Task.Execute()

VS version:

In VS 2015 zoom using Ctrl+Wheel does not work.

Hi,
I'm using Visual Studio 2015 Preview and the extension is not yet compatible.
Can the manifest be updated with the new 14.0 version support? I have no experience with extensions so I don't know exactly how the syntax works :)

Thank you

Problem is as said in Issue #3

Here is the Spy++ log:

log.zip

and part of it:

<000001> 00190CAA P WM_MOUSEWHEEL fwKeys:0000 zDelta:-120 xPos:877 yPos:464
<000002> 00190CAA P WM_MOUSEWHEEL fwKeys:0000 zDelta:-120 xPos:877 yPos:464
<000003> 00190CAA P WM_MOUSEWHEEL fwKeys:0000 zDelta:-120 xPos:877 yPos:464
<000004> 00190CAA P WM_MOUSEWHEEL fwKeys:0000 zDelta:-120 xPos:877 yPos:464
<000005> 00190CAA P WM_MOUSEWHEEL fwKeys:0000 zDelta:-120 xPos:877 yPos:464
<000006> 00190CAA P WM_MOUSEWHEEL fwKeys:0000 zDelta:-120 xPos:877 yPos:464
<000007> 00190CAA P WM_MOUSEWHEEL fwKeys:0000 zDelta:120 xPos:877 yPos:467
<000008> 00190CAA P WM_MOUSEWHEEL fwKeys:0000 zDelta:120 xPos:877 yPos:467
<000009> 00190CAA P WM_MOUSEWHEEL fwKeys:0000 zDelta:120 xPos:877 yPos:467
<000010> 00190CAA P WM_MOUSEWHEEL fwKeys:0000 zDelta:120 xPos:877 yPos:467

In VS 2019.

This mouse I know has fine scrolling capability, it is why I downloaded this...only to find that it does not work. Can you support this???? This mouse should be a prime candidate for this plug in. 1200dpi.

The text is blurry a few tenths of second after scrolling finished. Then the text is synced to screen pixels and becomes sharp again.

This happens for all Animation speed values (Slow, Normal, Fast). I have the impression that because Slow scrolling is longer, the blur time will be shorter, so maybe the time before text becomes sharp again is actually fixed.

Expected behavior: as soon scrolling finishes, the text should become sharp again. This means that the time before it sync with screen pixels shouldn't be fixed, but depend on scrolling speed.

Just after scroll:

After waiting a few tenths of second:

This doesn't seem to do anything on precision touchpads, or in any case on the one of the Dell XPS 15...

Is it possible to add soft scrolling to all the other windows too, like the Solution Explorer?

It appears to automatically be enabled. I've restarted VS 2019. (It wouldn't install without it closed anyway.) I have another smooth scroll fix that was installed, but it also didn't work, and was disabled -- so it shouldn't impact your extension.

Any ideas what I could try?

I'm talking about VS2013 and 1.0.1 version of the extension.
Scroll seems to work with extension installed same way as it does without it - not smooth.
I checked with debugger what's going on, and it seems that PreprocessMouseWheel method does being called. No smooth scrolling effect with Logitech mouse though.

Can this extension be used for Visual Studio Code? Checking extension library I don't find it. If I download it what are instructions for applying to VSCode?

Exactly what it says on the can. It's buttery smooth if I have another window in focus and I move my mouse over to a background VS window and use the two finger scroll gesture on my Synaptics trackpad attached to my 2015 Razer Blade laptop. With the VS window in focus, same gesture scrolls by seven lines at a time - which is weird since with the extension disabled I had the two finger scroll set to scroll one line at a time. Any idea what could be causing this, or how can I debug the issue and / or provide any useful diagnostics?

I'm using the v2.0.2 of this extension with VS2019 16.2 on an HP laptop. In addition to running VS locally, I also frequently remote from the laptop into a Citrix VDI desktop and run the same version of VS there.

In the VDI, SmoothScroll works exactly as designed, and if I disable the extension there, I can see the old blocky scroll motion. But in local VS, the extension does not work. (I know that it used to work on the same laptop, in VS2017 and before the last Windows update.)

Obviously, it's the same trackpad being used to drive local VS and VS on my VDI. It's also the same version of the extension and the same version of VS. But my VDI is running Win10 v1709, and my laptop is running Win10 v1903.

Is it possible that the Windows version has some effect here? Is there something else on my laptop that would have made the extension stop working?