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

Script editing history is not always correct #92420

Open
KoBeWi opened this issue May 27, 2024 · 1 comment
Open

Script editing history is not always correct #92420

KoBeWi opened this issue May 27, 2024 · 1 comment

Comments

@KoBeWi
Copy link
Member

KoBeWi commented May 27, 2024

Tested versions

4.3 dev6

System information

Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1060 (NVIDIA; 31.0.15.4633) - Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (8 Threads)

Issue description

While #63515 works reliably for the most time, there are some bugged cases that should be fixed. They are related to jumping to other script methods and autoloads.

Steps to reproduce

  1. Open the MRP.
  2. Open Base.gd and Second.gd
  3. In Second.gd Ctrl+Click on test(). You will be teleported to Base.gd
  4. Go back in history. You won't land directly at test(), there is some extra step in the history
  5. In Second.gd, Ctrl+Click on global (make sure Single.gd is not open)
  6. You will be teleported to Single.gd
  7. When you go back to history, the previous location is skipped and you'll end up in Base.gd
  8. Going forward will skip again to Single.gd. The middle step is gone

Minimal reproduction project (MRP)

JumpBugs.zip

@danbraik
Copy link

danbraik commented Jul 17, 2024

Hi, it is indeed a very annoying bug as it is essential for developping (all IDE have this feature for example with a keyboard shortcut). I was assuming it was already fixed in this version ^^'

I tried to use VScode as external program but it slows down the mental process by switching apps.
Have a nice day!

PS: Maybe related to godotengine/godot-proposals#954

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants