Uwe Raabe

https://docwiki.embarcadero.com/RADStudio/Athens/en/12_Athens_-_Release_2 https://docwiki.embarcadero.com/RADStudio/Athens/en/New_features_and_customer_reported_issues_fixed_in_RAD_Studio_12.2

Remember to manually uninstall all Parnassus plugins before you start the update! The auto-uninstall initiated by the setup is not able to handle that.

0 < x < Number of MMX users Proof: I am using it, which proves the lower limit You are not using it, which proves the upper limit Let alone that this number would give no usable insight, MMX could only add dropping these bookmarks to the usage report (which it doesn't). Using these bookmarks is an intrinsic IDE functionality which is not traced by MMX. After all, it is optional. Since I took over MMX I had exactly one question on how to disable or change one of these bookmarks, because it interferes with another plugin. Yours is the second. BTW, also since I took over MMX there has been no one sending any usage report (perhaps it just works on my tests but not in the wild), so I don't have any numbers of what people use most or least. While I would not drop any features based on such numbers, they would give me some hints of MMX features that may just be unknown and lack some promotion.

Sorry, GDPR.

None that I am aware of. Of course!

Extending my suggestion above, you can achieve this by creating a Group for all these breakpoints. Then add another breakpoint in the timer event, disable Break and select that group in Enable group. Add a similar breakpoint setting Disable group when you want to stop the log messages.

You can set a breakpoint in all possible methods and enter the Condition triggering it. In the Advanced view you can disable Break and set a Log message. This won't interrupt your debugging session and you can see the messages in the event log

In MMX Code Explorer properties look in General-Searching and History.

program Project1104; {$APPTYPE CONSOLE} {$R *.res} uses System.SysUtils, System.Classes, System.Types, Winapi.D3D11, FMX.Types3D, FMX.Context.DX11; type TDX11Context = class(TCustomDX11Context) private class var FResources: IInterfaceList; FVSSlot: ID3D11Buffer; FPSSlot: ID3D11Buffer; FVSSlotModified, FPSSlotModified: Boolean; FVSBuf, FPSBuf: array of Byte; FInputLayout: ID3D11InputLayout; FResourceViews: array [0..16] of ID3D11ShaderResourceView; FSampleStates: array [0..16] of ID3D11SamplerState; FBlendDesc: TD3D11_BLEND_DESC; FBlendState: ID3D11BlendState; FBlendStateModified: Boolean; FRasterizerDesc: TD3D11_RASTERIZER_DESC; FRasterizerState: ID3D11RasterizerState; FRasterizerStateModified: Boolean; FDepthStencilDesc: TD3D11_DEPTH_STENCIL_DESC; FDepthStencilState: ID3D11DepthStencilState; FDepthStencilModified: Boolean; FStencilRef: Integer; FBufferSize: TSize; end; TDX11ContextClass = class of TDX11Context; begin try RegisterContextClasses; if TContextManager.DefaultContextClass.ClassNameIs('TDX11Context') then Writeln(Length(TDX11ContextClass(TContextManager.DefaultContextClass).FVSBuf)) else Writeln('Oops!'); except on E: Exception do Writeln(E.ClassName, ': ', E.Message); end; ReadLn; end.

What is the exact error you get? When clicking on the link I get this:

I can reproduce with 12.1 here.

Please file a bug report at https://qp.embarcadero.com/

Which is actually six chars less than the with version. I can see no benefit in such with-V2 syntax. Local begin-end blocks without with, for or while have been part of the language since the beginning. With the advent of inline variables they may get some more use cases now. I would not call that fake in the first place.

Let's hope that it is not just that tool currently in action...

No, it has been mentioned in a private channel.

They are aware of it and working to get it right again.

Version V15.0.37 of MMX Code Explorer introduces Structured Difference Viewer (former available as a separate product). It is registered as an External Difference Viewer in the IDE and can be used as an alternative way to compare source files.

I can reproduce that. Please file a bug report at https://qp.embarcadero.com/

That would break compatibility with older Delphi versions. Either these changes have to be wrapped in some IFDEF directives or one has to specify at least Vcl.Imaging in Unit Scope Names of the project using the library.

The supported platform names can be found in PlatformConst.pas. It is what GetAllPlatforms returns.

Project Magician has an option for that:

pngimage.pas should never be compiled in 10.4.2. It is not even part of PngComponents as it already exists as Vcl.Imaging.pngimage.dcu in the Delphi library path. You should delete that pngimage.pas and probably pnglang.pas, too.

Just those have been identified as a potential source of problems recently.

Indeed, the OnChanging event would be a better place. Unfortunately it is triggered at least twice when AllowChange is set to False, even with the checks shown above.

If no one posts a solution there simply probably is none.