Skip to content

Fixes Multi-caret selection not working right#121

Merged
tig merged 7 commits into
developfrom
multi-caret
May 15, 2026
Merged

Fixes Multi-caret selection not working right#121
tig merged 7 commits into
developfrom
multi-caret

Conversation

@tig
Copy link
Copy Markdown
Member

@tig tig commented May 14, 2026

Problems

  1. Ctrl+Click on a C# comment (//) makes both slashes show the multi-caret attribute — placing a caret on a //\ comment highlights both slash characters with the multi-caret inverted attribute instead of just the single character at the click position.

  2. Cannot Ctrl+Click above the main caret — additional carets can only be placed below the primary caret position, not above it.

Changes so far

  • Moved \multi-caret.md\ from \�xamples/ted/docs/\ to \Docs/Help/\ for better discoverability.
  • Appended multi-caret editing documentation to \Docs/Help/selection.md.

tig and others added 7 commits May 13, 2026 09:45
Move multi-caret.md from examples/ted/docs/ to Docs/Help/ and append
multi-caret editing documentation to selection.md.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The drag handler (LeftButtonPressed | PositionReport) fired after every
Ctrl+Click press and called ExtendCaretTo, which moved the primary caret
to the click position and created an unwanted selection. This made it
impossible to place additional carets above the primary, and caused both
slashes of '//' to appear highlighted when clicking on a comment (the
primary cursor ended up on one slash while the additional caret overlay
painted the other).

Fix: track _suppressDragUntilRelease — set on Ctrl+Click press, cleared
on release — so the drag handler ignores PositionReport events that
follow a multi-caret click.

Also restore the normal attribute after MultiCaretRenderer.Draw to
prevent any future attribute leak to adjacent cells.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The simple foreground/background invert was not visually distinct enough.
Switch to Underline|Blink on the normal colors so secondary carets stand
out clearly from both regular text and selection highlights.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…quences

Add FAQ section to README documenting font ligature visual artifacts.
Cell buffer and ANSI output are provably correct — the visual bleed
users see with fonts like Cascadia Code or Fira Code is a terminal
rendering issue, not an Editor bug.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@tig tig merged commit ec44f7e into develop May 15, 2026
8 checks passed
@tig tig deleted the multi-caret branch May 15, 2026 12:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant