starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-25 08:24:54 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Mouse input from PDCurses application not working #10576

New Issue
Closed
opened 2026-01-31 02:24:58 +00:00 by claunia · 10 comments
claunia commented 2026-01-31 02:24:58 +00:00
Owner
Copy Link

Originally created by @thomthom on GitHub (Sep 10, 2020).

Environment

Windows build number: Microsoft Windows [Version 10.0.19041.450]
Windows Terminal version (if applicable): 1.2.2381.0

Any other software?
PDCurses: https://github.com/wmcbrine/PDCurses @ 618e0aa

Steps to reproduce

# CMakeLists.txt
cmake_minimum_required(VERSION 3.17)

project(CursesTest VERSION 0.1.0 LANGUAGES CXX C)

find_package(Curses REQUIRED)

set(MOUSECURSE_SOURCES
  mousecurse.cpp
)

add_executable(mousecurse ${MOUSECURSE_SOURCES})
target_link_libraries(mousecurse
  curses
)
target_compile_definitions(mousecurse PRIVATE PDC_NCMOUSE)

// mousecurse.cpp
#include <iomanip>
#include <iostream>

#include <curses.h>

void print_input(int input);

int main()
{
  initscr();
  raw();
  keypad(stdscr, TRUE);
  noecho();

  mousemask(BUTTON1_CLICKED, nullptr);

  move(1, 1);
  attron(A_BOLD);
  printw("PDCurses Mouse Test");
  attroff(A_BOLD);

  bool run = true;
  while(run) {
    refresh();
    int input = getch();

    switch(input) {
    case 'q':
      run = false;
      break;
    default:
      print_input(input);
    }
  }

  endwin();
  return 0;
}

void print_input(int input)
{
  move(3, 1);
  clrtoeol();
  printw("The pressed key is ");
  attron(A_BOLD);
  if (input & KEY_CODE_YES) {
    const char* name = keyname(input);
    printw("%i (%s)", input, name);

  } else if (input == KEY_MOUSE) {
    MEVENT event{};
    if(getmouse(&event) == OK) {
      const char* name = keyname(input);
      printw("%i (%s) [x: %i, y: %i, state: %lu]",
          input, name, event.x, event.y, event.bstate);
    }

  } else {
    printw("%i (%c)", input, input);
  }
  attroff(A_BOLD);
}

Expected behavior

I'm expecting the receive mouse input to the application. This works in normal cmd.exe:

mousecurse-cmd

Actual behavior

In Windows Terminal the mouse events doesn't reach the application, instead a text selection is made:

mousecurse-winterm

Originally created by @thomthom on GitHub (Sep 10, 2020). # Environment ```none Windows build number: Microsoft Windows [Version 10.0.19041.450] Windows Terminal version (if applicable): 1.2.2381.0 ``` Any other software? PDCurses: https://github.com/wmcbrine/PDCurses @ [618e0aa](https://github.com/wmcbrine/PDCurses/commit/618e0aaa31b4728eb4df78ec4de6c2b873908eda) # Steps to reproduce ```cmake # CMakeLists.txt cmake_minimum_required(VERSION 3.17) project(CursesTest VERSION 0.1.0 LANGUAGES CXX C) find_package(Curses REQUIRED) set(MOUSECURSE_SOURCES mousecurse.cpp ) add_executable(mousecurse ${MOUSECURSE_SOURCES}) target_link_libraries(mousecurse curses ) target_compile_definitions(mousecurse PRIVATE PDC_NCMOUSE) ``` ```cpp // mousecurse.cpp #include <iomanip> #include <iostream> #include <curses.h> void print_input(int input); int main() { initscr(); raw(); keypad(stdscr, TRUE); noecho(); mousemask(BUTTON1_CLICKED, nullptr); move(1, 1); attron(A_BOLD); printw("PDCurses Mouse Test"); attroff(A_BOLD); bool run = true; while(run) { refresh(); int input = getch(); switch(input) { case 'q': run = false; break; default: print_input(input); } } endwin(); return 0; } void print_input(int input) { move(3, 1); clrtoeol(); printw("The pressed key is "); attron(A_BOLD); if (input & KEY_CODE_YES) { const char* name = keyname(input); printw("%i (%s)", input, name); } else if (input == KEY_MOUSE) { MEVENT event{}; if(getmouse(&event) == OK) { const char* name = keyname(input); printw("%i (%s) [x: %i, y: %i, state: %lu]", input, name, event.x, event.y, event.bstate); } } else { printw("%i (%c)", input, input); } attroff(A_BOLD); } ``` # Expected behavior I'm expecting the receive mouse input to the application. This works in normal `cmd.exe`: ![mousecurse-cmd](https://user-images.githubusercontent.com/192418/92738958-b405e180-f37c-11ea-9f62-061a7ac46031.gif) # Actual behavior In Windows Terminal the mouse events doesn't reach the application, instead a text selection is made: ![mousecurse-winterm](https://user-images.githubusercontent.com/192418/92739049-c718b180-f37c-11ea-871c-0b565ac9736a.gif)
claunia added the Resolution-Duplicate label 2026-01-31 02:24:58 +00:00
claunia commented 2026-01-31 02:24:59 +00:00
Author
Owner
Copy Link

@jdebp commented on GitHub (Sep 10, 2020):

If it helps in diagnosis, PDCurses uses ReadConsoleInput() to read mouse input events. 48b0c12975/wincon/pdckbd.c (L575)

@jdebp commented on GitHub (Sep 10, 2020): If it helps in diagnosis, PDCurses uses `ReadConsoleInput()` to read mouse input events. https://github.com/wmcbrine/PDCurses/blob/48b0c1297529758a10a68aca0f904f90893f165d/wincon/pdckbd.c#L575
claunia commented 2026-01-31 02:24:59 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 10, 2020):

So, this is a /duplicate of #376! PDCurses applications are Windows applications using the Win32 console APIs to read mouse events, and we don't currently have support in the translation layer (which is also used by ssh and other terminal emulators on Windows) for translating Win32 mouse events from VT mouse events.

@DHowett commented on GitHub (Sep 10, 2020): So, this is a /duplicate of #376! PDCurses applications are Windows applications using the Win32 console APIs to read mouse events, and we don't currently have support in the translation layer (which is also used by ssh and other terminal emulators on Windows) for translating Win32 mouse events from VT mouse events.
claunia commented 2026-01-31 02:24:59 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Sep 10, 2020):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Sep 10, 2020): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
claunia commented 2026-01-31 02:24:59 +00:00
Author
Owner
Copy Link

@thomthom commented on GitHub (Sep 10, 2020):

Ok, I'm subscribing to the other issue. Thanks for confirming.

Are there other libraries that are currently able to achieve this in Windows Terminal? (PDCurses was the main library I found that has a working Windows implementation. ncurses seems to not support Windows.)

@thomthom commented on GitHub (Sep 10, 2020): Ok, I'm subscribing to the other issue. Thanks for confirming. Are there other libraries that are currently able to achieve this in Windows Terminal? (PDCurses was the main library I found that has a working Windows implementation. ncurses seems to not support Windows.)
claunia commented 2026-01-31 02:25:00 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 10, 2020):

That's a good question. I'm not sure of that off the top of my head...
In general, anything that wants to use VT is going to be a little easier to wrangle, and be a bit more cross-platform, but was likely not originally developed for Windows. 😄

@DHowett commented on GitHub (Sep 10, 2020): That's a good question. I'm not sure of that off the top of my head... In general, anything that wants to use VT is going to be a little easier to wrangle, and be a bit more cross-platform, but was likely not originally developed for Windows. :smile:
claunia commented 2026-01-31 02:25:00 +00:00
Author
Owner
Copy Link

@thomthom commented on GitHub (Sep 10, 2020):

What does "VT" stand for?

@thomthom commented on GitHub (Sep 10, 2020): What does "VT" stand for?
claunia commented 2026-01-31 02:25:00 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 10, 2020):

Ah, sorry. "Virtual Terminal". I typically call the in-band signalling sequences that terminals use to communicate (and applications use to communicate with terminals) "VT", though I can't determine why I do that. They do things like set color, request input mode changes ("encode these keys differently", "i want mouse input", etc.), and a whole heap of other things.

Broadly and loosely, they're the cross-platform alternative to the Win32 console APIs. Where somebody might say SetConsoleTextAttribute(FOREGROUND_RED) on Windows, they might print out the string \e[31m everywhere else.

@DHowett commented on GitHub (Sep 10, 2020): Ah, sorry. "Virtual Terminal". I typically call the in-band signalling sequences that terminals use to communicate (and applications use to communicate with terminals) "VT", though I can't determine why I do that. They do things like set color, request input mode changes ("encode these keys differently", "i want mouse input", etc.), and a whole heap of other things. Broadly and loosely, they're the cross-platform alternative to the Win32 console APIs. Where somebody might say `SetConsoleTextAttribute(FOREGROUND_RED)` on Windows, they might print out the string `\e[31m` everywhere else.
claunia commented 2026-01-31 02:25:01 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 10, 2020):

(This is very broad, and very loose, but it serves to illustrate the point. jdebp could almost certainly furnish a better explanation than the one that I spent 50 seconds on 😄)

@DHowett commented on GitHub (Sep 10, 2020): (This is very broad, and very loose, but it serves to illustrate the point. jdebp could almost certainly furnish a better explanation than the one that I spent 50 seconds on :smile:)
claunia commented 2026-01-31 02:25:01 +00:00
Author
Owner
Copy Link

@thomthom commented on GitHub (Sep 11, 2020):

So, I could use this "Virtual Terminal" from my app to get mouse events in Windows Terminal, as a workaround until WT supports it?

If so, what APIs would I be looking at?

@thomthom commented on GitHub (Sep 11, 2020): So, I could use this "Virtual Terminal" from my app to get mouse events in Windows Terminal, as a workaround until WT supports it? If so, what APIs would I be looking at?
claunia commented 2026-01-31 02:25:01 +00:00
Author
Owner
Copy Link

@jdebp commented on GitHub (Sep 15, 2020):

"VT" in this context usually comes from the product names of the DEC VT range of computer terminals, the VT05 to the VT525. It stands for "video terminal", in opposition to a paper or a hardcopy terminal.

@jdebp commented on GitHub (Sep 15, 2020): "VT" in this context usually comes from the product names of the DEC VT range of computer terminals, the VT05 to the VT525. It stands for "video terminal", in opposition to a *paper* or a *hardcopy* terminal.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Resolution-Duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#10576
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?