Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #873
Based on conversations within #873 I'd originally thought it'd be useful to be able to provide the mouse location in pixels and in cells, however upon further reflection this would require that crossterm hold state of what the most recent cell size was (which would change with each Resize) - hence I think the best way we can address this is to simply allow for users to get the mouse size in pixels and provide tooling for users to get the cell size in pixels themselves and hold this state, so if necessary the user is able to easily calculate the cell coordinates as well whenever they need it.
This PR has 3 main changes
EnableMousePixelCapture
)cell_size()
) [CAN MAYBE REMOVE]cargo run --features="event-stream" --example event-stream-tokio-pixels
)OPEN QUESTION:
s
you will see the difference in both calculations@bbb651 @joshka