Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refine IViewportRange API to use 'cursor positions' for x value #2512

Merged
merged 1 commit into from
Oct 25, 2019

Conversation

Tyriar
Copy link
Member

@Tyriar Tyriar commented Oct 25, 2019

Fixes #2484

@Tyriar Tyriar added this to the 4.2.0 milestone Oct 25, 2019
@Tyriar Tyriar requested review from mofux and jerch October 25, 2019 11:44
@Tyriar Tyriar self-assigned this Oct 25, 2019
Copy link
Contributor

@mofux mofux left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

Copy link
Member

@jerch jerch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@@ -308,7 +308,7 @@ export class Linkifier implements ILinkifier {
if (matcher.hoverTooltipCallback) {
// Note that IViewportRange use 1-based coordinates to align with escape sequences such
// as CUP which use 1,1 as the default for row/col
matcher.hoverTooltipCallback(e, uri, { start: { row: y1 + 1, col: x1 + 1 }, end: { row: y2 + 1, col: x2 } });
matcher.hoverTooltipCallback(e, uri, { start: { x: x1, y: y1 }, end: { x: x2, y: y2 } });
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thats a win compared to the left side 👍.

@Tyriar Tyriar merged commit 4fe5a5a into xtermjs:master Oct 25, 2019
@Tyriar Tyriar deleted the refine_range branch October 25, 2019 11:48
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.

Close on decision regarding 0-based and 1-based coordinates in API
3 participants