Uwe Raabe

MMX allows to configure all actions as well as disable any action. If some are missing please send a bug report to support@mmx-delphi.de

Could it be that you open the datamodule while a VCL project is open? Usually the IDE stores the used framework in the project file.

Can it be that you have ParentFont = True in your forms?

Uninstalling by default keeps the registry (which is the desired behavior for an update). Fortunately it ask for it, so you are able to decide otherwise. If you want to remove Delphi completely, you simply have to say so.

MMX uses an internal formatting scheme which is not adjustable. You need to re-format your code manually or with the IDE formatter.

Seems your command window uses codepage 850: var encoding := TMBCSEncoding.Create(850); try Result := encoding.GetString(pBytes); finally encoding.Free; end;

Can you attach the binary stream content here?

I have several applications running fine on High DPI (even built with D10.4), but that may just depend on the specific applications. Just to give a rough estimate: It took me about six weeks to get MMX Code Explorer working with D10.4 and there are still glitches like cut-off texts or overlapping controls. Most of them are not Delphi related, but lie in the nature of scaling integer values.

What is the result when doing it this way? TEncoding.ANSI.GetString(pBytes)

Sorry, seems I have bin mislead.

Start Delphi 11 (DPI Unaware) from your Window start menu

Seems some settings made it over the Uninstall/Reinstall sequence.

Looks like you missed to select the C++ Builder when installing while something on your system still requires it. Was this a vanilla installation or did you somehow use some settings from a previous or other one?

AFAIK, that is not implemented. Local variables are no items in the explorer tree (like fields, methods or properties) and the Convert to Field action can handle only explorer items. This means that implementing such a functionality is not trivial. A workaround would be place the cursor at the first assignment of the local variable and use <Strg>-<Alt>-F to add a new field. In most cases the type is automatically detected. Either before or after that just delete the local variable manually.

AFAIK, the underlying Windows control doesn't support that.

That exactly describes a blocking behavior. As long as the specification says blocking and you want non-blocking, you better change the specification first before doing anything with the code.

AFAIK, that won't work with Inserts via SQL (at least I never did it that way). The reason may be, that an INSERT query will never retrieve any fields like a SELECT query. There simply are no fields you can get the ID from. The usual way you have something like SELECT * FROM MYTABLE which retrieves all fields including the ID field. For adding a new record you just call Append or Insert, set the field values as needed and call Post. If everything is set up correctly, the new ID should then be available in the PERSON_ID field.

Can you explain what you see as the benefits of the aware mode while accepting to not being able to read the tiny forms?

It can be found on the status line:

The breakpoints are store in the DSK file - either project or the project group one, depending what you have opened.

Yes.

I actually gave it a try on 10.4, but I have difficulties to distinguish the tiny icons then. I admit to have a higher scale than only 125%

This is standard for D11 and it works quite well when you use the scaled designer, too. Unfortunately that will change your DFM files often in an unwanted way. As long as you are the only one working with these files it might be acceptable, but in mixed environments it is often not really usable in the moment. Seems that Embarcadero itself doesn't make use of the scaled designer: All PixelsPerInch in the form resources of CoreIDE280.bpl are 96 DPI.

Can you please elaborate on that?

DPI unaware mode doesn't hinder you to write DPI aware applications with Delphi, which works pretty well meanwhile. It is just that the IDE runs at 96 dpi internally scaled by Windows.