-
Notifications
You must be signed in to change notification settings - Fork 5.8k
8261931: IGV: quick search fails on multi-line node labels #2889
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
Conversation
Remove line breaks from the 'label' property that is searched on by default.
👋 Welcome back rcastanedalo! A progress list of the required criteria for merging this PR into |
@robcasloz The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
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.
Does this solution work on all platforms?
Thank you for fixing this problem.
I think "\R" here refers to the "Line Breaker Matcher"
As the document says, it matches any linebreak sequence in Unicode. I assume this linebreak sequence comes from the text control. All platforms should have the similar linebreaks. Therefore, it's portable. I also verified this patch on MacOS. It works. Instead of replacing \R with " " for label only, Is it a better place to do that in resolveString()?
The reason is Figure.getWitdh() for lines. I don't think it can get appropriate width if the string contains \R. |
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.
LGTM
Hi Nils, thanks for bringing up multi-platform support. From now on I will test platform-sensitive IGV changes on both Windows and Linux. This change works on Linux and MacOS (as reported by @navyxliu, see also his comment about the use of "\R"). I just tested it on Windows and it also works as expected: |
Thanks for the feedback @navyxliu!
I cannot reproduce this problem, do you have an example where a node's width is not properly adjusted? |
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.
Looks good to me!
@robcasloz This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 160 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
Thanks for reviewing, Nils! |
I can't see any problem either. Forget it. Your patch looks good to me. thanks! |
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.
Looks good!
Another thing that I've noticed in Tool
-> General
: There is no response when clicking the Apply
button. Is it even mapped to an action? When clicking Apply
and then Cancel
it has not applied the changes. Maybe the button can also just be or removed. But that can be handled in another RFE.
Thanks for reviewing, Christian!
Right, at the moment this is just an effectless leftover from the NetBeans platform. I will make a note about it. |
Sounds good. |
/summary |
@robcasloz Setting summary to |
/integrate |
@robcasloz Since your change was applied there have been 160 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit f6b4ba0. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
This change makes it possible to match any field of a multi-line node label, by removing line breaks from the
label
node property that is searched on by default.Tested manually using different node label configurations (configurable in
Tools
->Options
->General
), with and without line breaks.Progress
Issue
Reviewers
Download
$ git fetch https://git.openjdk.java.net/jdk pull/2889/head:pull/2889
$ git checkout pull/2889