-
Notifications
You must be signed in to change notification settings - Fork 177
[Win32] Properly encapsulate cursor handle creation and disposal #2403
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
Merged
HeikoKlare
merged 2 commits into
eclipse-platform:master
from
vi-eclipse:cursor-disposal-CursorHandle
Aug 11, 2025
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just a Nit: The handle field still stores the raw long, while
zoomLevelToHandle
stores theCursorHandle
. This introduces a risk of the two becoming out-of-sync if the logic changes in the future. IMO It might be cleaner to store theCursorHandle
directly in handle and callthis.handle.getHandle()
(or rename the method to getNativeHandle() for clarity) wherever the long handle is needed @HeikoKlareThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's true that the two values may get out of sync but that's actually not different from the current state.
CursorHandle
is immutable, so it will be as consistent to the currenthandle
value as it was before. We need to get rid of thehandle
, but that's something that will be done with the lazy generation of handles implemented by Shahzaib.