Lars Fosdal

https://docwiki.embarcadero.com/RADStudio/Athens/en/Android_Devices_Supported_for_Application_Development#Intel-based_Android_Devices recommends a couple of apps that can verify the capabilties of your Android device.

@dummzeuch - I think it is commendable to do your testing on a low powered setup. If it works satisfactory there, it will rock on higher end gear.

Vote here Native ARM64 compiler for Windows for ARM https://quality.embarcadero.com/browse/RSP-38298 Context: https://www.theverge.com/2022/5/24/23139475/microsoft-visual-studio-2022-native-arm-vs-code

uncertainty, doubt - Is it unthinkable that the codegen would be scheduled for improvements when adding support for Windows for ARM?

@A.M. Hoornweg It is always helpful to indicate what kind of error you get, and where you get it.

Less hearsay/leaks - more acknowledged facts, please.

https://learn.microsoft.com/en-us/windows/win32/api/securitybaseapi/nf-securitybaseapi-gettokeninformation BOOL GetTokenInformation( [in] HANDLE TokenHandle, [in] TOKEN_INFORMATION_CLASS TokenInformationClass, [out, optional] LPVOID TokenInformation, [in] DWORD TokenInformationLength, [out] PDWORD ReturnLength ); TokenInformationLength should be the size of the TokenInformationClass?

"rabbit whole" ... /sigh Yeah, I guess it is... still, it is a far cry from clean code.

We've given up on HighDPI. It is just not worth the effort and grievance for a project that has entered care and maintenance, even if the users would greatly benefit from it.

I've gone even deeper down the rabbit whole and referenced object instances through the tag... I am not proud of it.

Only the visible rows will render the icon.

You'll should find a 64-bit Midas DLL in your redistributable folder: C:\Program Files (x86)\Embarcadero\Studio\23.0\Redist\win64 See also:

Well, the English CoPilot knew. But, the Norwegian one did not.

It supposedly was a trivial question.

Did you use the offline installer or the web installer? If you used the offline installer, please see: http://docwiki.embarcadero.com/RADStudio/Sydney/en/Release_Notes.

I sort of assumed that 16777619 in that code was a prime, but wanted to check... ChatGPT 4o mini said "No". So, I asked CoPilot in Norwegian - and it said "No" (Nei) On a whim, I then asked it in English LLMs - Lovely Lying Machines.

I have very few packages (The Parnassus debacles, FastReports, FMXLinux) and a couple of non-packaged (TMS VCL UI Pack, EurekaLog), so I usually just do it manually. As for FD connections, I have my own wrapper lib that gets the connection points from configs per app (which can be retrieved from wherever I want),

While I don't disagree with the characterization of LinkedIn, I do find it handy to keep in touch with people I've worked with. I've practiced some restraint on adding people, so my list is mostly limited to people I've actually been in touch with. Also, it has become a fairly interesting place to follow certain companies.

Had to reinstall TMS VCL UI Pack, but EurekaLog appears to be ok...

I use a global function GetNextInstanceNumber to get and increment a integer variable and just set the name to Self.ClassName+'_'+GetNextInstanceNumber.ToString;

Make sure to uninstall the Parnassus plugins before installing the patch.

Note that the Frame instance should have its parent set to Owner as well.

It seems you can emulate auto increment, using a trigger and a generator?

https://quality.embarcadero.com/browse/RSP-41961 The process of cleaning up circular references can be quite challenging, as we today have no good tool to discover and track the unit interdependcy. "Blatant" circular references are explicitly forbidden, but since we can include units both in the interface and the implementation section - it is quite easy to circumvent this rule. Another challenge is when you inadvertently drag in a massive collection of units into your project, because someone needed a structure or function from a specific unit - which again uses other units, which uses others again - and so forth. The discovery of where this unit is included, and when in the compilation it is parsed, would be significantly helped by a simple build log. A sequential log of the compilation of each unit in the application - indicating where it first was necessary to compile another unit to complete the current unit. I suggested it could look something like this - more comments in the QP issue. Pls vote/comment if you find it interesting. unit1 compiling... unit2 compiling... unit3 compiling... unit3 compiled (lines, warnings, hints) unit2 compiled (lines, warnings, hints) unit1 compiled (lines, warnings, hints)

How about an untyped Multiplier and MULTIPLIED_CONSTANT = 1E-11 * NativeInt(MULTIPLIER); ?