Not detecting VS Code

[ameeruljunaidi]

Hi,

For some reson it's not detecting VS Code.

For example, when I try to select the window using or , the cursor is not jumping to the window.

EasyClick also does not work.

I am using VS Code Insiders (but it didn't work for normal VS Code either) on a Window 10 x64 machine.

[pit-ray]

Thank you for using it.
It may be undiscovered bugs, so I want more details.

Let me know what key-bindings do not work (e.g. gg, t).
And, please check log files in ~/.win-vind/log/ after its behavior.

By the way, in my test environment, EasyClick works in VS Code.

VSCode: 1.54.3 (Stable), 1.55.0 (Insiders)
Windows 10: Home 64bit 20H2 Build 19032.867

[ameeruljunaidi]

Hi, I'm not entirely sure what happened, but I restarted win-vind and it now works, thank!

[fdawans]

Thank you for your software.
I have been looking for such a thing for a while but there was nothing satisfying on Windows.

EasyClick does not work for me in VSCode 1.58.2 , I am using win-wind 4.0.1 and Windows 10 Enterprise 10.0.17134.
I only see a 'D' in the middle of the screen.
Edit: Also same issue with Teams 1.4.00.18264 (64-bit).

[pit-ray]

I only see a 'D' in the middle of the screen.

Hi.
Thanks for using win-vind.
Maybe once you click on the area inside the window, hints should appear. We are currently redesigning the implementation of this factor. Please wait for a while.

[fdawans]

Thank you for the feedback.
If I click inside, it is also not working.
I will already learn to use it in all the other apps and wait for the new version, good luck!

[pit-ray]

Hi.
I have just published the pre-release. Please try it and let me know if you have the same problem.
Thanks.

[fdawans]

Hello,
I tried win-vind_4.2.1 and EasyClick is still not working in VSCode (same as before, only a D in the middle of the screen).
I am running the portable version (no admin rights).

See attached log.

error_202110092325.log

[pit-ray]

Thanks for the details.
I am currently building the same environment as yours. Please wait for a while.

[pit-ray]

Today, I tried Windows 10 1803 x64 and was able to reproduce the same issue.

Since it works fine on the latest Windows 10 and Windows 11, it may be due to minor differences in Windows API. Until I know more about the cause, we will specify it as an issue in the README.

Thanks.

[fdawans]

Thank you for your help, that's really not easy!
I just saw that my company just pushed an update, from 1803 (RS4) to 1909 (19H2).
I will let you know if it works.

Edit: working on 1909

[pit-ray]

I'm glad it works!
I will check the API differences between 1803 and 1909. And keep this issue open until I know more.
Thanks.