pyscripter

I believe they do among other styles. (see images in the home page) @Carlo Barazzetta Can you enlighten us on this?

Good alternative styled Task Dialog implementation: EtheaDev/StyledComponents: Components similar to Delphi VCL Buttons, Toolbar, DbNavigator, BindNavigator, ButtonGroup and CategoryButtons with Custom Graphic Styles, and an advanced, full-customizable TaskDialog, also with animations!

[RSP-41990] Style the Windows Task dialog (Vcl) - Embarcadero Technologies

Not quite. See for instance Ohh...WinUI3 is really dead! - When can we expect the announcement? · microsoft/microsoft-ui-xaml · Discussion #9417 The Microsoft strategy for GUI App development is utterly messed up: WinForms WPF Xamarin Forms UWP WinUI3 MAUI And there is no longer a GUI designer. You have to develop XAML in a text editor. Discussion: WinUI 3.0 XAML Designer · Issue #5917 · microsoft/microsoft-ui-xaml

FWIW, the latest version of GExperts from Experimental GExperts Version – twm's blog installs and works fine here with Delphi 12.3.

Yes I do notice the difference. However I do not have 10.4 installed to compere. Delphi 12 behaves the same as Delphi 11 though.

Are you using Vcl? Are you using styles? I can see that in your images the form title bars are styled differently. I don't see that in a simple dialog: Delphi 11: Client width 269, Width 285 Delphi 12: Same.

Four of my reported issues were fixed in 12.3: TStackPanel spacing property is not DPI scaled - RAD Studio Service - Jira Service Management Unnecessary painting of styled scrollbars on mouse move - RAD Studio Service - Jira Service Management Memory leak when you use Vcl.IMouse - RAD Studio Service - Jira Service Management The Panning Window is not DPI scaled - RAD Studio Service - Jira Service Management Four are still open.

This is the 64 bit IDE. My problem was that the Win64 platform was not available. After trying many things, I had to do a full uninstall/install to get the platform available again.

After upgrading to 12.3 I do not get the Win64 platform. Only Win32. Anyone has the same issue? Any ideas how to fix it?

Of course it does. What you are doing is like running the following python script: exec("a = 1; print(a)") exec("b = 1; print(a)") a is created in the first statement and still exists when the second statement is executed. but if you do exec("a = 1; print(a)", {}, {}) exec("b = 1; print(a)", {}, {}) then the second statement raises an error. ExecFile has the following signature: procedure ExecFile(const FileName: string; locals: PPyObject = nil; globals: PPyObject = nil); If you provide no arguments for locals and globals, the code is executed in the namespace of the __main__ module. If you do not want this to happen then you should provide empty dictionaries as arguments for the locals and globals parameters (or just the locals). But then MainModule.VALUE will raise an error. Example code (not tested): var Py := GetPythonEngine; var NewDict := NewPythonDict; Py.ExecFile('python1.py', ExtractPythonObjectFrom(NewDict)); var val := NewDict.GetItem("VALUE"); NewDict := NewPythonDict; Py.ExecFile('python2.py', ExtractPythonObject(NewDict)); val := NewDict.GetItem("VALUE"); // will raise an error since VALUE does not exist VarClear(NewDict);

Indeed. Python variables are reference counted. As long as you keep a reference the python object it refers to is kept alive. When you have a statement like: var s:Variant :=MainModule.MYVALUE s is a custom variant that stores the python reference. The variable will be dereferenced, when s goes out of scope or you explicitly clear s (VarClear(s)).

The issue was closed within minutes... Explanation:

Issue submitted: https://embt.atlassian.net/servicedesk/customer/portal/1/RSS-2959

I was really asking whether you see any technical reason that I am missing. Because, otherwise it is such an obvious omission.