starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Drawing a button? #7095

New Issue
Closed
opened 2026-01-31 00:54:52 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 00:54:52 +00:00
Owner
Copy Link

Originally created by @Richienb on GitHub (Mar 22, 2020).

With the addition of mouse support, is it possible to simulate buttons in the Windows Terminal?

Originally created by @Richienb on GitHub (Mar 22, 2020). With the addition of mouse support, is it possible to simulate buttons in the Windows Terminal?
claunia commented 2026-01-31 00:54:53 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Mar 22, 2020):

With the addition of mouse support, is it possible to simulate buttons in the Windows Terminal?

Yes. You can test this with the Linux dialog utility. In a WSL bash shell, try something like this:

dialog --yesno "Click Yes or No" 5 20 && echo Yes clicked
@j4james commented on GitHub (Mar 22, 2020): > With the addition of mouse support, is it possible to simulate buttons in the Windows Terminal? Yes. You can test this with the Linux [`dialog`](https://linux.die.net/man/1/dialog) utility. In a WSL bash shell, try something like this: dialog --yesno "Click Yes or No" 5 20 && echo Yes clicked
claunia commented 2026-01-31 00:54:53 +00:00
Author
Owner
Copy Link

@Richienb commented on GitHub (Mar 22, 2020):

@j4james Is there a demo with code that I can use or an implementation guide for this?

@Richienb commented on GitHub (Mar 22, 2020): @j4james Is there a demo with code that I can use or an implementation guide for this?
claunia commented 2026-01-31 00:54:53 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Mar 22, 2020):

The general idea is you enable up/down click events by setting private mode 1000 ("\e[?1000h"). And then you can just read the events from stdin in the form of an escape sequence, in the same way you'd read a keypress event.

There are a bunch of a different reporting modes you can choose from, depending on whether you need a wider coordinate range, or you want to know the state of modifier keys, etc. Have a look at the Terminal Guide website for a nice explanation of the different options, and the format of the reports. But note that some formats are better supported than others. Windows in particular only supports modes 1000, 1002, 1003, 1005, and 1006 (at least for now).

Anyway, that's the low level protocol, but depending on what programming language and operating systems you're targeting, there may be higher level libraries you can use (e.g. ncurses). I'm not sure this is the best place to ask for example code though.

@j4james commented on GitHub (Mar 22, 2020): The general idea is you enable up/down click events by setting private mode 1000 (`"\e[?1000h"`). And then you can just read the events from stdin in the form of an escape sequence, in the same way you'd read a keypress event. There are a bunch of a different reporting modes you can choose from, depending on whether you need a wider coordinate range, or you want to know the state of modifier keys, etc. Have a look at the [Terminal Guide](https://terminalguide.netlify.com/mouse/) website for a nice explanation of the different options, and the format of the reports. But note that some formats are better supported than others. Windows in particular only supports modes 1000, 1002, 1003, 1005, and 1006 (at least for now). Anyway, that's the low level protocol, but depending on what programming language and operating systems you're targeting, there may be higher level libraries you can use (e.g. [ncurses](https://en.wikipedia.org/wiki/Ncurses)). I'm not sure this is the best place to ask for example code though.
claunia commented 2026-01-31 00:54:54 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 23, 2020):

This is a fine discussion, and by all means, feel free to continue it here, but since there's nothing really actionable for the Terminal team here, I'm going to close this issue. Thanks!

@zadjii-msft commented on GitHub (Mar 23, 2020): This is a fine discussion, and by all means, feel free to continue it here, but since there's nothing really actionable for the Terminal team here, I'm going to close this issue. Thanks!
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 Area-Input Area-VT Issue-Question Needs-Tag-Fix Needs-Triage Resolution-Answered
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#7095
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?