This lets users coming from other editors such as Sublime Text or Atom continue to use the keyboard modifier they are familiar with. VSCode developers have introduced a new setting, editor.multiCursorModifier, to change the modifier key for applying multiple cursors to Cmd + Click on macOS and Ctrl + Click on Windows and Linux. So, recent versions of VSCode let you toggle between Alt+LeftMouse and Ctrl+LeftMouse under the Selection menu, as detailed in another answer.Īlternately, you could change your OS key bindings using gsettings as mentioned in another answer.Īdd multiple cursors with Ctrl / Cmd + Click Ubuntu) assign window dragging to Alt+LeftMouse, which will conflict with VSCode. This makes it a lot easier to introduce multiple cursors select 300 lines and only 80 fit in the viewport). If the find widget is open, then the find widget settings (matchCase / matchWholeWord) will be used for determining the next occurrenceĬtrl+U ( Cmd+U on Mac) undoes the last cursor action, so if you added a cursor too many or made a mistake, you can press Ctrl+U ( Cmd+U on Mac) to go back to the previous cursor state.Īdding cursor up or down ( Ctrl+Alt+Up / Ctrl+Alt+Down) ( Cmd+Alt+Up / Cmd+Alt+Down on Mac) now reveals the last added cursor to make it easier to work with multiple cursors on more than 1 viewport height at a time (i.e.
More multi-cursor features are now available in Visual Studio Code 0.2:Ĭtrl+D ( Cmd+D on Mac) selects next occurrence of word under cursor or of the current selectionĬtrl+K Ctrl+D moves last added cursor to next occurrence of word under cursor or of the current selection This works on Windows and Linux*, and it should work on Mac, too. In fact, the fix was so simple I was pretty skeptical about it actually working (it only took a minute or two and when the process was done, it was so fast and simple, I’m like, there’s no way that worked.Press Alt and click.
I was so defeated to see that the link for the sony support basically brought me to the same site where it seems the link for the firmware update or calibration tool I needed was missing, but the supplementary link provided by Commenter worked! My screen is back! I was ready to give up and accept that I had lost touch screen functionality but it was such a quick and easy fix. and then I came across this site kind of randomly and was basically in the mindset of this is really the last hope.
I felt like I explored every link, video, support, etc. I was so discouraged and ready to give up. This worked for me and hopefully it will be able to help other people.Įverything I tried hadn’t worked.Leave the tool to run and don’t touch the screen during the process, after it completes and exits the touch screen will be fixed. Navigate to that folder and run the file CalibG4.exe.
How to fix non responsive areas on a Surface Pro touch screen I found a thread on Reddit where users had a similar problem and managed to fix it via a driver/calibration tool from N-TRig (the makers of the touch screen). On my Surface the lower 3 rd of the touch screen worked ok but most of the time the upper section didn’t respond. At first I thought it was an issue running Windows Insider builds but after a bit of research it seems it’s down to a calibration issue. I recently had a very strange issue with the touch screen on my Surface Pro 3 where some areas wouldn’t respond to touch but would work ok with the pen.