TiGü

PowerShell is a powerful scripting language and you will find lot of materials (youtube, tutorials, books) about it.

Try something like that for I := 0 to myPlateTuple.Length - 1 do begin var Sub := myPlateTuple.GetItem(I); end; see:

First, maybe that helps: https://stackoverflow.com/a/6616121 Do you use this? https://github.com/maerlyn/old-delphi-codes/blob/master/_KOMPONENSEK/Comms.pas Check for Mainthread with a construct like procedure TForm62.comportclient1Receive(Sender: TObject; InQue: Integer); begin if TThread.Current.ThreadID = MainThreadID then begin SendMessage(handle, pm_ProcessBarcodeScan, WPARAM(0), LPARAM(0)); Application.ProcessMessages; end; end;

Check TNotificationWinRT.Create. I assume your lNotification is freed before it used here. constructor TNotificationWinRT.Create(const ANotificationCenter: TNotificationCenterWinRT; const ANotification: TNotification); var DeleateActivate: TNotificationCenterDelegateActivated; DelegateDismiss: TNotificationCenterDelegateDismiss; DelegateFailed: TNotificationCenterDelegateFailed; begin FToast := TToastNotification.Factory.CreateToastNotification(TToastTemplateGenerator.GetXMLDoc(ANotification)); DeleateActivate := TNotificationCenterDelegateActivated.Create(ANotification); FDelegateActivatedToken := FToast.add_Activated(DeleateActivate); DelegateDismiss := TNotificationCenterDelegateDismiss.Create(ANotificationCenter, ANotification.Name); FDelegateDismissToken := FToast.add_Dismissed(DelegateDismiss); DelegateFailed := TNotificationCenterDelegateFailed.Create(ANotificationCenter, ANotification.Name); FDelegateFailedToken := FToast.add_Failed(DelegateFailed); end;

The "Debug DCU" option is checked in the project options? Only with this you can debug in VCL and RTL source code (System, Winapi, etc.). Anyway, the use of Application.ProcessMessages looks like a code flaw and is the wrong approach in most cases.

unit REST.Types // Delphi 10.4 ... type //at line 123 /// <summary> /// Content /// </summary> TRESTContentType = (ctNone, ctAPPLICATION_ATOM_XML, ctAPPLICATION_ECMASCRIPT, ctAPPLICATION_EDI_X12, ctAPPLICATION_EDIFACT, ctAPPLICATION_JSON, ctAPPLICATION_JAVASCRIPT, ctAPPLICATION_OCTET_STREAM, ctAPPLICATION_OGG, ctAPPLICATION_PDF,... // <-------

I know, this thread is a little bit dated, but I take a look to your github repository. https://github.com/fpiette/OvbImgOrganizer/blob/main/Source/Direct2D_1/Vcl.Direct2D_1.pas Have you ever tried to change your SwapEffect in DXGI_SWAP_CHAIN_DESC1? You use DXGI_SWAP_EFFECT_DISCARD in Line 1207 but the most recent examples recommend DXGI_SWAP_EFFECT_FLIP_DISCARD or DXGI_SWAP_EFFECT_SEQUENTIAL_DISCARD. https://docs.microsoft.com/en-us/windows/win32/api/dxgi/ne-dxgi-dxgi_swap_effect Maybe you should use just the normal Present-Method of the Swap Chain. So, just write DXGISwapChain.Present instead DXGISwapChain.Present1 and get rid of the PresentParams : PDXGIPresentParameters because you don't use it anyway. https://social.msdn.microsoft.com/Forums/en-US/4737f4f6-68a4-45eb-8941-13f68802153a/why-direct2d-idxgiswapchain1present1-is-much-slower-than-directdraw?forum=windowssdk https://walbourn.github.io/care-and-feeding-of-modern-swapchains/ Are you familiar with the DirectX debug layers? So, if you do something fishy with your DirectX stuff, the Debug Layers will tell you in the (Debug) Event Log (you must read both links). It's a great help during development: https://docs.microsoft.com/en-us/windows/win32/direct3d11/using-the-debug-layer-to-test-apps https://docs.microsoft.com/en-us/windows/win32/Direct2D/direct2ddebuglayer-overview Please add D2D1_DEBUG_LEVEL_INFORMATION to FactoryOptions.DebugLevel before calling D2D1CreateFactory and D3D11_CREATE_DEVICE_DEBUG to the CreationFlags before calling D3D11CreateDevice. If you wrap it between {$IFDEF DEBUG} and {$ENDIF}, you have a clean Release code.

Does it work? Do you see a difference between the various interpolation modes?

You can check if your normal ID2D1RenderTarget/ID2D1HwndRenderTarget/ID2D1DCRenderTarget from the TDirect2DCanvas supports the newer Direct2D 1.1 ID2D1DeviceContext. Something like this: // Self.Handle is the HWND of your Form... FVCLCanvas := TDirect2DCanvas.Create(Self.Handle); var DeviceContext: ID2D1DeviceContext; if Supports(FVCLCanvas.RenderTarget, ID2D1DeviceContext, DeviceContext) then begin var YourPointer: Pointer; var DontForgetThePitch := 1024; var AllImportantBitmapProperties: D2D1_BITMAP_PROPERTIES1; var D2D1Bitmap: ID2D1Bitmap1; DeviceContext.CreateBitmap(SizeU(1024,1024), YourPointer, DontForgetThePitch, @AllImportantBitmapProperties, D2D1Bitmap); DeviceContext.DrawImage(D2D1Bitmap, nil, nil, D2D1_INTERPOLATION_MODE_HIGH_QUALITY_CUBIC); end; I assume you will find out the details on your own (Fill the Pointer to your Data, Pitch, Bitmap props). Or you build the entire Direct 2D 1.1 - 1.3 thing by yourself and forget the crappy TDirect2DCanvas. Microsoft had a lot of DirectX samples and all of them have a abstract class called "DirectXBase" (e.g. https://github.com/microsoft/VCSamples/blob/master/VC2012Samples/Windows 8 samples/C%2B%2B/Windows 8 app samples/Direct2D interpolation modes sample (Windows 8)/C%2B%2B/DirectXBase.cpp). You can use the attachment pascal unit as a starting point. I recommend the header translations from MfPack (https://github.com/FactoryXCode/MfPack) for this. DirectXBase.pas

I assume aQry and bQry are of the Datasnap.DBClient.TClientDataSet type? Please remove the Sleep(100) call and put all the logic after if bQry.RecordCount > 0 then ... in the AfterOpen event handler from bQry (see https://docwiki.embarcadero.com/Libraries/Sydney/en/Data.DB.TDataSet.AfterOpen).

I had the same problem today in my Delphi 10.4. After some searching and comparing with a newly created registry key for Delphi, I found out that it is due to the disabled entries in the IDEInsight key. Example: [HKEY_CURRENT_USER\SOFTWARE\Embarcadero\BDS\21.0\IDEInsight] "Disabled0"="Project Options" "Disabled1"="Components" "Disabled2"="Object Inspector" "Disabled3"="New Items" "Disabled4"="Open Files" "Disabled5"="Recent Files" "Disabled6"="Recent Projects" "Disabled7"="Component Palette" "Disabled8"="Code Templates" "Disabled9"="Desktop SpeedSettings" "Disabled10"="Projects" "Disabled11"="Files" "Disabled12"="Forms" "Disabled13"="Commands" "Disabled14"="Preferences" After deleting the complete key in the registry and restarting Delphi, IDE Insight worked again.

No, you or someone else can do. Feel free. I'm not affected by this behavior (as a german).

Project1.dpr

In my example screenshot the font is the same for both editors.

Please stop to wonder about the font(s). It does not matter! The problem is the text rendering itself in the editor of the Delphi IDE. In the screenshot you can see a few examples in the Delphi IDE and in Visual Studio Code. In both cases, the font is the famous Consolas from Microsoft (https://en.wikipedia.org/wiki/Consolas). Most european languages like German, Swedish or Hungarian are well rendered. Even Greek is displayed nice. But all others looks like a pile of shit. Arabic is broken, Thai has to much space between the symbols. The same problem occours in Khmer and Sinhala (mispelled as Shinghal in the source code). Chinese look okay, but not perfect. Conclusion: The Delphi IDE Editor is designed for European character sets only.