efortier

At some point, everything stops working; Find declaration, Error insight, etc. When that happens, try the following. I am not sure it will work for you, but for me that was the cause of so many aches that I made an expert that does it for me. Try this: 1- Delete ALL .DCU files that your project or the DelphiLSP can see. For me, that was *.DCU in my project directory. 2- From the tools menu, restart the LSP server. 3- Wait 5-15 seconds. For me, this solves the problem. Note: a "Clean" does not fix the problem for me because there are always some DCU file left. I found out that when the LSP server encounters some DCU file it completely stops working. And since a lot of the IDE functionality is based on the server, a lot of things break. Very janky workaround. This has been going on since Delphi 12. Someone at Embarcadero told me the disabling of "legacy" code in Delphi (refactoring, find references, etc) will allow them to rebuilt the features better and improve the LSP. Right now, the sad state of release 13 prevents me from using it. HTH!

Hi all, I'm trying to find what is the meaning of those and what the compiler does with variables declared with with either [out] or [in], like these: TMyRecord = record [in] SrcPosition: TPoint; [out] DstPosition: TPoint; end; I've been trying to search on google and in the doc, but all I can find is references to the normal in and out keywords. Thanks!

This problem is my main gripe with Rio. And it's not only a cosmetic problem with Error Insight. When I try to refactor and rename a class for example, any function or procedure in a unit past an inline var declaration will not get renamed, which screws up the whole refactoring. And Undo refactoring does not work in this case. In this screenshot of a personal project, I tried to rename "TGameStates" to "TGameStateManager". The class names in green were renamed, the ones in red were not. This seems like a pretty serious bug and while I've been using Delphi since v1.0 and I'm used to this kind of things by now, I am sadden to see something like this not fixed before release. I've been a fan of Delphi forever, and the company I work for has a 5 year plan in place to phase Delphi out and switch to a yet unannounced replacement, and that too makes me sad because we're all sure it'll be Visual Studio and C#.