Brandon Staggs

That RSS is not visible to me for some reason. What was your workaround? We're finding that some unusual configurations fail PxToDP -> DpToPx on version 12.3. Looking at the code it just doesn't seem like it can work properly in all cases.

My initial testing shows that Grok knows more about Delphi x-plat development than Embarcadero's LLM does.

Someone forgot to tell the guy who made the splash screen then.

Once again, it seems that Delphi's strength is the fact that there are legacy applications locked into it. The cost of abandoning millions of lines of code is far greater than continuing with an IDE that appears to be on life support with failing equipment. No refactoring. No code formatting. Yeah, I get that refactoring didn't work well and that lots of people (myself included) did not trust CTRL+D. But this is not a modern IDE. It just isn't. You can't remove basic functionality like refactoring and pretend to be a professional IDE. A couple of weekends ago I set up VS Code to write and debug 6502 assembly on an attached emulator. It was astonishingly smooth. It was fun to use. Everything just works. If it wasn't for the difficulty of dealing with hundreds of visual forms I would be looking into getting a Delphi build environment working in VS Code.

I think "past me" is my least favorite developer to work with.

They are rarely (never?) all available on release day.

This is the only viable solution.

Seriously, show the whole unit.

I'm glad you did post this here! Thank you! Alas, it does not resolve debugging speed issues on MacOS 15.4+.

I don't understand what you mean by that. Bottom line: inc files still exist and work just like they always have: If you include a file its contents are placed in-line where you include it when the unit is compiled. Where that "right place" to include it is, depends entirely on what you are roping into your unit. "Useful records" definitely do not make sense as inc files. Source code included in Delphi uses inc files extensively and I wish it didn't. It makes understanding the units and navigating source take longer. There are good reasons to use inc files, such as defining compiler directives that you need to be consistent across multiple units, but if your "stuff" can just be made into units, then it should not be placed in inc files. IMO. :-)

You may as well just stuff all your classes into a single unit so you can achieve this. You don't need the language to undergo a fundamental redesign. As projects grow the issues with circular references can become annoying. I know this well. But the solution is to do better class design, not to embrace the excessive coupling of the classes.

Good information in this thread. @David HeffernanI was actually interested in your reasons for not using SameValue and what you use as an alternative.

Why is it lethal to puppies?

No serious developers are interested in binary-only Delphi components.

Used Apple's support for dual-boot to install Sonoma. Debugging works perfectly fine there.