Leaderboard

Now where would be the fun in that?

The problem even shows up in the IDE. and the cure is the same as for compiled code

No idea how that screen shot error is relevant to ICS, we don't use openssl.exe. Our openssl zips have a different versions of openssl.exe in the Win32 and Win64 zips, you have mixed therm up. Angus

Hello, Google Gemini (please don't even give it a try). ChatGPT 3.5: Correct Translation ChatGPT 4.0: Pro Translation Thanks to all the advice.

I should simply stop posting without actually checking shit... object Label1: TLabel Left = 303 Top = 233 Width = 99 Height = 15 Caption = 'Text'#32'Text' end does however, work correctly. Edit But if you actually edited the dfm text and put in that #32, then view as form, and back to view as text - it has been converted to 'Text Text'. As @Lajos Juhászpoints out - Unicode text that is entered in the form attribute editor, will translate to #1234 values.

Are you using an EXE compressor such as AsPack by any chance? AV programs don't like compressed executables.

Perhaps this did the trick: https://en.delphipraxis.net/topic/11151-delphi-and-use-only-memory-safe-languages/?page=5&tab=comments#comment-90366

I'll avoid direct pointer math when I can, but when you need to drive video, text, and geometry effects dynamically, live at 60fps, it helps to know theses things and use them where optimization is needed.

SHIFT + Windows key + S, allows to capture a part of the screen via click and drag the mouse.

Consequent use of interface references (with rerf counting for lifetime control) instead of object references avoids that problem completely.

I have it and many of the techniques in it that were great 10-15 years ago are totally unnecessary today and even detrimental with modern CPUs. It's still a good read and even though some techniques are obsolete, knowing them can help solving other similar problems simply because they can make you think about problems differently. Um... Always? There used to be a time, not that long ago, when integer math was far superior to floating point math (see: Hackers Delight). Not so anymore. via https://stackoverflow.com/questions/2550281/floating-point-vs-integer-calculations-on-modern-hardware The video is a bit long so I haven't watched it yet, but it's LEA: Load Effective Address, "LEAL" is AT&T syntax for LEA (Intel syntax). Here's a good comment on the topic by Peter Cordes: Using LEA on values that aren't addresses / pointers? Before you start replacing all your shifts with LEA you should be aware that it isn't always faster. As with almost everything in modern CPUs it depends on what the CPU is otherwise busy with. https://stackoverflow.com/questions/70316686/assembly-why-is-lea-eax-eax-eaxconst-shl-eax-eax-const-combined-fast

Could be related to String with non-ASCII characters directly attached to a #xx or #$xx literal corrupts the final string Current workaround is to use a + operator to concatenate the parts.

Nobody kehrs ( https://images.app.goo.gl/jtQZNqxjkAh559Do9 ) People, who don't know Delphi, will not touch it. People, who like Delphi will continue to use it People, who use Delphi but don't like it (any more) will continue to use it until they find an alternative. Any new buzzword bullsh*t will not change that. To translate: low code = RAD no code = does not exist

Again? What was old is new again - except my jokes.