Is the Delphi 12.2 Error Insight, completion and CTRL+Click completely broken ?

[John R. 20]

I've just migrated from Delphi 12.0 (due to some internal exceptions and problems) to 12.2 with patch 2 and I'm baffled by its error insight, code completion and ctrl+click not working most of the time for my projects.

I'm loosing so much time opening other units which are right next to the current one to see the definition of an object's method that I'm wondering if I shouldn't have stayed with the old 12.0. Restarting the LSP doesn't work either.

Is it a bad installation on my part or a known problem ?

I'm still waiting for components vendors to officially support 12.3 but I'm wondering if it is event better than 12.2 at this point. Any feedback from users who updated ?

Having worked with many other fantastic IDEs (VSCode, VS, PhpStorm or Rider to name a few), I'm really worried that this is taking so much time for Delphi's IDE to have these basic code editor features working most of the time.

 

PS: I know that Marco Cantu mentioned that the LSP will be reworked in the future, and that VS code could be used as an alternative but none of those really help me at the moment.

[dummzeuch 1593]

I have heard from others that they still have this problem with Delphi 12.3, but I have not seen this problem in my projects. I had it with several Projects in Delphi 10.2 though  (which in turn work fine With Delphi 2007 and 12.3 though)

 

Just an aside: GExperts has got an option in the Uses Clause Manger to look up the Unit that contains an identifier declaration (e.g. a Class type, but not a method) and open that unit with the cursor set to the line that contains this declaration. That's not quite the same functionality, but it might mitigate your problem a little bit.

[Mark NZ 9]

For us many features (including those 2) are broken or work poorly in many recent versions of Delphi (10.x onwards?) when working in large projects, still so in Delphi 12.3

[John R. 20]

Finally, LSP is working and I can work again! In case it helps anyone, here are a few random remarks about this behavior:

• I have 4 projects in the project group and the error insight was completely non-functional only on one of those projects, the biggest one
• Oddly enough, when the broken project was open, if I open a unit from another project, it works for that unit but not for any units included in the broken project 🤯
• My VM has plenty of memory and cores, the LSP never crashed while it wasn't working and I could see multiple instances of it in process explorer
• I tried with LSP on VS Code and obviously the same problem occurred, which is at least a coherent behavior
• I believe that the number of sources available in library path was the problem. What fixed it for me:
  • Update to latest Spring4D 2 and used DCUs instead of sources
  • Removed sources from DevExpress and used DCUs only