PeterPanettone

1. Collapse the procedure/function: 2. Click on the line number to select the entire (now hidden) code of the procedure/function. 3. Press CTRL+C to copy the entire code of the procedure/function. This is particularly useful for longer procedures/functions. It also works in Delphi 13.

OK, here is another one:

OK, here is another simple trick I often use to quickly jump to specific locations in very large units (e.g., 20,000 lines, like in my upcoming "Advanced Windows Start Menu"): We could use simple bookmarks for this purpose, but I often clear them all after finishing a specific short-term task. So we need something more persistent: 1. Create these kinds of comments on the locations you want to jump to quickly: implementation // toc_implementation public // toc_public // toc_PrivateVariables private // toc_private TForm1 = class(TForm) // toc_MainFormClass // etc. 2. Then put all these TOC items at the very top of your huge unit: {TOC: toc_implementation toc_public toc_PrivateVariables toc_private toc_MainFormClass } 3. Then, when you need to quickly jump to one of these locations in your huge unit: - Press CTRL+Home to jump to the top of the unit - Double-click one of the toc_ items to select it - Press F3 to quickly jump to this location This will save you a lot of search time!

Does anyone have an updated version of wuppdi Welcome Page for Delphi 11 Alexandria?

You are so right. That is exactly the right way to look at AI. Unfortunately, AI is also becoming a tool for political oppression. And thank you for the humorous part.

Do you think AI is becoming a new religion?

You are right, DOCUMENTATION is everything. AI-generated code without accompanying documentation is dangerous (SUPERGROK always links to documentation for anything it generates). However, I strongly reject "regulation" laws from a criminal organization as the so-called "EU" (EU ≠ Europe).

Generally, AIs often make mistakes or hallucinate when asked advanced questions about Delphi code. The most reliable AI for Delphi code is SUPERGROK.

Possible scenarios for the upcoming 128-bit technology: • Specialized applications such as scientific calculations or cryptography could benefit from it • Very large databases or in-memory computing could potentially require it • New areas of application that we cannot foresee today

You too, have a nice day.

Why are you repeating this to me? Sorry, but I can't help you.

Then it is probably a HighDPI interference. Tell me the specifics of your monitor.

You should know that computer programs are not deterministic, especially complex computer programs like the Delphi IDE. So, a statement like "but it works on my computer!" is a typical statement from computer illiterates.

Like many code editors, the Delphi source code editor (both 12 and 13) has a useful feature: Clicking the Line Number selects the whole Line. This allows you to easily copy an entire single line by first clicking on a Line Number and then pressing CTRL+C. However, this does not work when clicking on the LAST DIGIT of a line number! Is this a bug or a configuration issue? Or is it due to HighDPI interference?

The SmartSearch principle is very simple: function ContainsSearchTerm(const AText, ASearchTerm: string): Boolean; // returns True if: // if ASearchTerm is single word: if AText contains ASearchTerm // if ASearchTerm is multiple words (devided by space): if AText contains all words var LWords: TArray<string>; LWord: string; begin // Return False if ASearchTerm is empty if System.SysUtils.Trim(ASearchTerm) = '' then Exit(False); // Split search term by space LWords := ASearchTerm.Split([' ']); // If there's only one word, check if AText contains that word if System.Length(LWords) = 1 then begin Result := System.StrUtils.ContainsText(AText, ASearchTerm); end else begin // Multiple words: AText must contain all words Result := True; for LWord in LWords do begin if not System.StrUtils.ContainsText(AText, LWord) then begin Result := False; Break; end; end; end; end; Here is a shorter optimized version: function ContainsSearchTerm(const AText, ASearchTerm: string): Boolean; var LWords: TArray<string>; LWord: string; begin // Split search term by space, filter out empty words LWords := Trim(ASearchTerm).Split([' ']); if Length(LWords) = 0 then Exit(False); // Check if AText contains all non-empty words for LWord in LWords do if (LWord <> '') and not ContainsText(AText, LWord) then Exit(False); Result := True; end;

Do you have a particular reason for hating jokes - perhaps if they are not 64-bit? 😉

Obviously, you didn't read what I wrote. I wrote: "removing the search box content with the BACKSPACE key". 1. For example, enter "kirk" 2. Then, remove the whole content "kirk" with the backspace key. 3. Result: Not all 104 items are restored.

I think I've found the bug: When entering something in the search box and then removing the search box content with the BACKSPACE key, the search box content is not really removed but only made INVISIBLE. Only when clearing the search box content by clicking on the "x" pseudo button, the search box content is really removed. That's a common bug that often occurs in Delphi development when a feature is not carefully tested.

Is there a bug in Delphi 13 GetIt? When using the search criteria 'All/Date/All', only these six items are displayed (despite the right-aligned number 104 for All):

Is dummzeuch an Illuminati expert? Do Illuminati experts hate jokes?

On my large screen, the menu font was very small after installation. So I increased the User Interface font size to 12: A restart of the IDE was needed to see the changes. But now the text size on the welcome screen is ridiculously large, while the menu text size is just right: Isn't there a way to set the font size of the menu separately? That would be what we call USER-FRIENDLY.

They provide an UGLY default background image (Lights at the Night Circus.jpg), which distracts from the text. However, there are currently no font settings for the Welcome Page.

Technically, this does not explain the striking jump in the folder name's version number from 23 to 37. Perhaps they wanted to avoid any connection to the unlucky number 13?

One significant enhancement to the Delphi language would be the addition of support for strings as case selectors, similar to Free Pascal. Currently, the case statement is limited to ordinal types (such as integers, characters, or enumerations), which enables compile-time optimizations like jump tables for superior efficiency compared to chained if-then-else statements. However, Embarcadero could extend the compiler to maintain this performance for ordinal types while also supporting strings—perhaps by internally compiling string cases to equivalent if-then-else logic at runtime, as Free Pascal demonstrates. This would provide developers with greater flexibility without compromising existing code.

We have now created this feature request: https://embt.atlassian.net/servicedesk/customer/portal/1/RSS-4079