Change:
* Creates a new NativeImage instance from the NSImage that maps to the given image * name. See NSImageName for a list of possible values. The hslShift is applied to * the image with the following rules This means that [-1, 0, 1] will make the <del> * image completely white and [-1, 1, 0] will make the image completely black. In * some cases, the NSImageName doesn't match its string representation; one example * of this is NSFolderImageName, whose string representation would actually be * NSFolder. Therefore, you'll need to determine the correct string representation * for your image before passing it in. This can be done with the following: echo * -e '#import <Cocoa/Cocoa.h>nint main() { NSLog(@"%@", SYSTEM_IMAGE_NAME); }' | * clang -otest -x objective-c -framework Cocoa - && ./test where SYSTEM_IMAGE_NAME * should be replaced with any value from this list. </del> <ins> * image completely white and [-1, 1, 0] will make the image completely black. In * some cases, the NSImageName doesn't match its string representation; one example * of this is NSFolderImageName, whose string representation would actually be * NSFolder. Therefore, you'll need to determine the correct string representation * for your image before passing it in. This can be done with the following: echo * -e '#import <Cocoa/Cocoa.h>nint main() { NSLog(@"%@", SYSTEM_IMAGE_NAME); }' | * clang -otest -x objective-c -framework Cocoa - && ./test where SYSTEM_IMAGE_NAME * should be replaced with any value from this list. </ins> */ static createFromNamedImage(imageName: string, hslShift: number[]): NativeImage; /**

Discussion:
<!-- Please search existing issues to avoid creating duplicates. --<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: --Since the 1.36 update, every single time i click on anything inside VS Code, the onscreen keyboard pops up and the VS code window resizes to fit the screen that's left. I tried reinstalling 1.35 and that fixed the issue. I also tried installing the insider build and the issue was there too. VS Code is the only program or window it seems that makes the onscreen keyboard appear so it's not an issue with the keyboard. Plus going to the earlier version fixed it. I am using a 2-in-1 tablet pc and this is happening when the screen is docked with a keyboard attached. Basically, it seems like VS code doesn't know a keyboard is attached and keeps making the onscreen keyboard pop up when it thinks you want to enter text. <!-- Use Help Report Issue to prefill these. --- VSCode Version: 1.36 OS Version: Windows 10 32-bit Does this issue occur when all extensions are disabled?: Yes
did we do anything special here for the Web.
can you check if this happens in other applications too? E.g. Chrome?
They on-screen keyboard only comes up with the newest VS code version. 1.36 and the insider build which i tried. It's really consistent with just this program. And every time i click on anything where it might expect me to enter text. I made sure the setting for "Show the touch keyboard when not in tablet mode " is set to off in typing settings. I tried turning it on and when i do, the onscreen keyboard still pops up all the time in VS code but for other programs, it only pops up if i click something with my finger on the touchscreen and not the mouse. I also tried the trackpad on the keyboard and its the same with the onscreen keyboard popping up in just VS Code.
Somewhat related:
any clues?
whats the build version of windows 10 you are running ? Also can you try launching vscode with the following flag see if there is a difference. Thanks!
I tried launching vscode insiders from the command line with those flags and it didn't make a difference.

The only thing that seems to stop the keyboard from popping up is disabling the touch keyboard from services but then I cant use it for anything else. Im using windows version 1511 build .1176 Its an older computer with an Atom processessor. Z3735F 2GB Ram.
thanks for testing, but based on this chromium issue comment , it seems there are issues with windows version less than RS4 . But the fact that you are seeing this issue only with vscode and not chrome is a bit confusing. I will get a touch device tomorrow and try to narrow down the source of this issue. In the meantime is it possible for you to update the windows version ?
I didn't realize my windows version was so old. I'm using an old tablet. It doesn't seem to be able to update windows beyond what I have now.
can you also mention the windows 10 build version you are running ? Also can you download the chromium browser from here which is the same version stable release uses and check if the issue is present. Thanks! I tried to verify the issue on Lenovo thinkpad X1 Carbon with windows 10 build version 1903 but wasn't able to.
Can you also see if you are able to workaround the issue temporarily by launching vscode with /cc
I couldn't run the version of chromium you linked because i'm using 32-bit windows but I did find a version with a similar date that was 32 bit and it's causing the same issue of the on-screen keyboard popping up. I downloaded win32rel579575_chrome- Also i tried launching vscode the way you said to disable usb keyboard input and it made no difference. Im using windows version 1511 build .1176
I'm using Windows 8.1 - Windows_NT x64 6.3.9600
Thanks for testing! I was able to find a similar issue in upstream , will try to backport the fix and see if it resolves the issue.
Thanks for replying so quickly.

Version: 1.35.1 (system setup) Commit: Date: 2019-06-12T14:30:02.622Z Electron: 3.1.8 Chrome: 66.0.3359.181 10.2.0 V8: 6.6.346.32 OS: WindowsNT x64 6.3.9600 Sorry, but I had to downgrade to 1.35.1 so that I could continue development. Let me know if Yeppoh's feedback isn't sufficient and I'll try the other things you suggested. Regards, itbgcthate __ From: Robo <: Friday, July 5, 2019 2:43 PM To: microsoft/vscode Cc: itbgcthate; Mention Subject: Re: [microsoft/vscode] The on-screen keyboard opens anytime i click on anything inside VS Code () you also mention the windows 10 build version you are running ? Also can you download the chromium browser from here which is the same version 1.36 stable release uses and check if the issue is present. Thanks! I tried to verify the issue on Lenovo thinkpad X1 Carbon with windows 10 build version 1903 but wasn't able to. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread
Should this have been fixed in 1.36.1? I'm seeing the same behavior.
the fix from electron has not been released yet, will update here once we have a release with the fix. Thanks!
Same issue here. I'm also using an older Windows tablet with an older 32-bit build. Thanks for investigating this!
Same issue, downgraded to 1.35.1 and the issue went away