Leaderboard

If I am among the suspects I would have to disappoint. I agree that it is likely related to thread ownership of the string passed. That is why in old code you often see the use of a record type or short strings allocated in the calling thread and freed in the receiving thread. Like a flaming bag of dung thrown over a wall...up to the receiver to dispose of it.🤣

@Mike Torrettinni Nothing special, I thought you like exotic methods 😉

Press F7 or F8 to start the debugging session for the application and in CPU View on the code pane press ctrl+g and enter $0040DD41. Which line is it in the code? But It's a low address, so it will be most likely system.pas, so you have to look after the call stack, either on AV or by putting a breakpoint there with a condition. Also, there is an inherited; in the message handler, how do the other handlers look like?

I'm afraid that both the points stated here are factually incorrect. SendMessage synchronously sends a message to a window. The code is executed by the thread that owns that window. Secondly, there is no reason why code in one thread should not operate on a string variable allocated in a different thread. That's not even what's going on anyway. It's just a pointer to null terminated character array. And the message handler receives that and makes a new string. No problem there.

Yes, as per the article. Make sure you're actually deploying the font files (Project|Deployment in the Delphi IDE), and to the correct Remote Path. i.e: .\ Also make sure that the entries in info.plist.TemplateiOS.xml match exactly with the actual filename - filenames are case sensitive on iOS.

Finally my 2cts: Using methods like Predecessor (or Successor) to access an index based on the amount of items in a container would just hurt my brain to much. I also would always think that -1 or +1 is faster than calling some method, but then I'm the kind of developer that doe not inspect Delphis libs, I just use them and rely on documentation...a dying breed I know. But know this, all you Delphi RTL and VCL know-it-alls give Embarcadero an excuse to not maintain the online help. Please consider this comment tongue-in-cheek.