Lars Fosdal

curl -F emulates filling content on a web page and pressing enter. I've not used -F before, so I am not sure if the reference 'item' in 'item=something' identifies the field to be filled, and that the right side is what it should be filled with?

Why? It is stupid and annoying.

It is odd that it works with remote debug symbols enabled, though.

Something else I find annoying. EMBT insists on mailing me offers for products that I already subscribe to. Why? What are the odds that someone would add another license for Delphi at Black Friday, Week, Month, Xmas time, insert price reduction opportunity here?

Personally, I would probably not use such tools. The move from one visual component lib to another on a different platform is going to cause headaches. You would not want to do direct DB from a mobile device, you often can't use tabs and dialogs the same way - the UI form factor is different, touch vs mouse is different. If the biz logic is done in separate classes, such a move is not difficult to do manually. If it is tightly intertwined with GUI code - you will have a job on your hands. As for the state of Mida - the last update on their forums were in April 2019?

There have been a large number of theories about why this happened. File format has been ruled out. Windows Policy may be relevant - but with a workaround, I am not going to dig deeper.

Well, I didn't spot one - so none from me. A binary editor could be used to create one?

On a different note: Delphi-PRAXiS is not social media platform, so please stay on topic and contribute facts rather than speculation. Edit: I am not naming names - if you feel that I am addressing you, well, maybe I am 😛

Add FMXLinux to the GetIt packages that needs to be uninstalled before an upgrade.

@Uwe Raabe I can reveal that I am a happy user of Project Magician 🙂 - Option checked. No change.

Possible causes? A developer on a non-corporate laptop does not have this problem. Another developer on corporate laptops have the same problem as me on both new and old laptops. That seems to indicate a Windows policy may be a factor here. Anyways - Include remote debug symbols ticked gave back working breakpoints for us.

What is the default setting for Project | Options | Linking | Include remote debug symbols? It was off. On = I can debug. Locally.

I thought this was a new problem... then I tried on the old laptop again. Guess what - it fails in the same way there as well.

The size of the project does not seem relevant. The one that fails is about 600k lines. The tiny ones works just fine, as does the larger 1100k lines one.

Line endings was wrong at first (Thanks for nothing, GitHub) - but was corrected with a setting in GitKraken. The compiler warns if there if f.x. only LF instead of CRLF - but how to guard against a lonely CR?

I can't make sense of that statement.

Opened another, larger project. 1.1+ million lines. No problems. Debugs fine. Didn't even touch the .dproj.

Switched to Release, builded, exited Delphi. Restarted Delphi, switched to Debug, builded, ran - no change. No weird characters. Opens fine in TextPad, Notepad, VS Code and IDE.

See previous posts. Files are in UTF-8 format with BOM.

Fresh checkout from Git. Compiler does not complain. Program executes fine. It just that it doesn't appear to be in debug mode.

Another app, same problem - except this time, deleting the .dproj did not solve the problem. WTF is going on?

The downside of deleting the .dproj file. Output path, search path, dcu output path, and EurekaLog needs to be reconfigured. Oh, such joy.

The plot thickens: I deleted the .dproj for a specific app. Debugging worked. I opened a project group- containing the same app. Debugging stopped working. Guess I need to rebuild that too. Strike that. I ran the wrong project ><

Deleting the .dproj did solve the problem. I compared the newly created to the old one, and there was a huge amount of crap in the old one. But, why does it work on the old installation?

Yes - started a new project. Same problem. No! I closed all projects, then tried again with a brand new project. That worked.