-
-
Notifications
You must be signed in to change notification settings - Fork 21.5k
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
Fix jumping to function definition using Ctrl+LMB
or the "Lookup Symbol" button
#73196
Conversation
@akien-mga ok. So I have to wait for that and rebase my branch? |
Done, you can rebase and redo the relevant changes to fix #72353 + the regressions. |
It seems to me that this is not a solution for #73167. I will try to fix it too. |
71d2f05
to
6abc667
Compare
a330bdd
to
1cb9651
Compare
1cb9651
to
a0bfd7c
Compare
a44e103
to
266fff0
Compare
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.
I can confirm this fixes the issues, but can't tell if the implementation is correct.
cc @Paulb23 |
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.
ScriptEditor changes look good, agree with KoBeWi comments.
We could probably convert get_text_for_code_completion
to use the new method as well.
Given it touches CodeEdit
unit tests would also be nice to add.
…okup Symbol' button.
266fff0
to
56e2fad
Compare
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.
ScriptEditor side looks good.
Ctrl+LMB
or the "Lookup Symbol" button
Thanks! |
I'm facing an issue regarding lookup symbol and autocomplete suggestions not working on referenced children nodes. |
@nagidev No. I checked this for the previous commit, the result is the same. The reason is not in this PR. |
Fixes #72353.
Fixes #73167.
Fixes #73480.
I found the cause of bug #73167. The problem is that when we click on the
Lookup Symbol
button in the context menu, the methodString CodeEdit::get_text_for_symbol_lookup()
returns position of cursor which is located on theLookup Symbol
and wrong for code parsing.Such a bug found in the
3.5.1.stable
too.