Uwe Raabe

Might be tricky to persuade the third party lib to create your new classes rather than its own.

I'm probably going to regret it, but I'll throw this one into the discussion: function BlankControl(EditControl: TObject; const EditMess: string; ShowErrorMsg: Boolean; MaxLen: Integer): Boolean; begin Result := False; try if EditControl is TCustomEdit then Exit(length(trim((EditControl as TCustomEdit).Text)) < MaxLen); if EditControl is TComboBox then Exit(length(trim((EditControl as TComboBox).Text)) < MaxLen); if EditControl is TDBComboBox then Exit(length(trim((EditControl as TDBComboBox).Text)) < MaxLen); if EditControl is TDBRadioGroup then Exit((EditControl as TDBRadioGroup).Value = ''); if EditControl is TDBLookupComboBox then Exit((EditControl as TDBLookupComboBox).Text = ''); if EditControl is TDBCheckBox then Exit((EditControl as TDBCheckBox).State = cbGrayed); finally if Result then Showerror(EditControl, EditMess, false, ShowErrorMsg); end; end;

Ehm! That Exit call will only exit procedure gotoTrue, but not function BlankControl. Funny, that such a suggested improvement perfectly qualifies for the reason of this thread

Yes, here: Enumerated Types with Explicitly Assigned Ordinality

Put a TPanel in the grid cell and place the label and LED onto that panel. The vertical alignment of a TLabel is controlled by its Layout property,

As ProcessMessage already does all the work, there is not much to do in the body of this loop.

Well, obviously announcing is easier than implementing.

There definitely is a plan! The problem is how much of that plan turns into reality.

Would you mind writing in English, please? Otherwise a Personal Message would be a better choice.

I also use Delphi in many VMs. To overcome the installation limit I have switchen to a Network Named License and make use of my own license server (ELC). This allows me to install Delphi on as many VMs I want as long I have it running on up to three machines simultaneously.

That menu item should be enabled whenever you have the CPU window open while debugging.

SelectiveDebugging

The VCL already provides such a flag for you: TApplication.ModalLevel

Usually the MMX setup installs the app and also registers it into the Delphi IDE. You only have to select it as the default viewer.

I expect the dataset to be closed when SQL changes. Otherwise the records would not match the SQL anymore. One can easily extend this to all other properties that have influence on the data retrieved and the way it can be accessed. What would be the benefit of an immediate exception here? The author of the code wants to change the SQL, so what would be the gain from that exception (which happens at runtime btw.)? The dataset has to be closed anyway to change the SQL, so why not closing it automatically? Unfortunately this option is not available in the poll (at least as I understand it).

Of you compile with packages and allow external packages be loaded dynamically.

Both tools have a completely different approach. While DelphiAST analyzes source code, the class tree utility requires the classes to be compiled into the exe.

If possible, could you be a bit more specific? I mean, that is a bit vague, isn't it?

You have to activate that option:

You can define the group names per project in MMX Properties - Project options: A single identifier is treated as a group prefix which has to be followed by a dot (like System, VCL, FireDAC). You can also use wildcards like Rz* for all units from Raize Components (KSVC). Unit names not covered in one of the schemes above can be listet in brackets. This is the setting for MMX itself: (ToolsApi,DesignIntf,DCCStrs,DockForm,TabDock);Winapi;System.Win;System;Xml;Vcl;VirtualTrees*;Rz*;Tb*;Png*;MMX The settings are stored in the dproj file.

It needs some code to be added, but you can declare a const array[<enumeration>] of Integer with values 0 in all places where the enumeration is used in some way. const cCheckProjectType: array[TProjectType] of Integer = (0, 0, 0, 0); If you now extend TProjectType the compiler will stop at all places where such a declaration is present and you can inspect the code around for correct TProjectType usage. After that is done you extend the array values to make the compiler continue to the next problematic position.

Very good point 👍

Enclosing the loops with a qryItemReceita.DisableControls/EnableControls should help a bit.

You can still have the first, but nevertheless the second being active. Usually an UEFI BIOS can be made working as an old fashioned one. Unfortunately switching that back to UEFI mode requires some significant work to make Windows boot again.

Two things that are sometimes overlooked: UEFI BIOS TPM 2.0 For the second item there is an article (in German): Windows 11 läuft wohl nicht auf Intel-Macs