Patrick PREMARTIN

thanks

If you need to upgrade Windows 11 on this "old" VM it's possible even if Microsoft says "this system is too old, Windows Update can't be used anymore". I found how to do it on Parallels forum and can explain how to do it there.

Ah, yes, I've forgotten that. So no other solution than RTTI or checking all components in loops. Mark, you're probably not the first one in 30 years to want to access it. Perhaps you can open a "new feature" request on https://qp.embarcadero.com asking for having DataSources[] (read only) and DataSourceCount public properties on TDataSet ? (and explain why you need them)

Perhaps you can try to access it from a helper on TDataSet...

Developpez.com blocks some external site like Google Translate. Only the translation included in the web browser can work.

The help is an install option, like the samples. Restarting the installer or Tools / Manage Features allow to install/uninstall them. You can also go to https://docwiki.embarcadero.com/docs/products/rad_studio/ if you just want the help files on an other computer and don't have access to the online DocWiki

I've just created a sample project to illustrate what you can do. Check https://github.com/DeveloppeurPascal/Delphi-samples/tree/main/FireMonkey-Samples/027-StylesAndEXESize Screen samples are good for understanding how to use visual component stacking, layout and alignment, but not necessarily for organising things. Never put styles on forms but rather on data modules, like database components or image lists used by several files. This is something you learn as you use it, which you can read about in certain corners of the documentation or in the many books full of good practices. Unfortunately, it's difficult to add a comment in the examples, but a good idea for improvement.

Hi The things you do in the form editor is embed as a resource in the programs. If you fill your styles with more than one platform they are all embed in it. The solution is to use TDataModule as a TStyleBook container. One per platform or per platform/style. In the TDataModule unit, simple use compiler defines to compile or not the data module class depending on MSWINDOWS, ANDROID, IOS, MACO or LINUX defines. Condition the implementation the same way you do for the interface. In your code, do the same for the uses of these units and of course to enable or not the styles you want to use. It's a little work but it's easy to do and avoid having too big EXE/APK/IPA/APP files.

It was my second point, I've updated the post.

I'm glad to see that my videos are sometimes useful. 😉

Good to know. In projects used in older Delphi releases (or for open source) I suggest to replace the unit by this code if you still use FireDAC Encryption for SQLite : {$IF CompilerVersion >= 36.0} // Delphi 12 Athens FireDAC.Phys.SQLiteWrapper.FDEStat, {$ELSE IF CompilerVersion >= 34.0} // Delphi 10.4 Sydney FireDAC.Phys.SQLiteWrapper.Stat, {$ELSE} FireDAC.Phys.SQLiteWrapper, {$IFEND}

Modifying standard units can be a source of problems when you install a new update or major release. It's better you add your own implementation. In FMX it's simple : - ShowModal of a form for Windows, Mac, Linux - For iOS / Android, using a Rectangle for the background (to catch the click events) and your design in front of it. A TFrame shown with an alignment contains and it's done. You can also use https://github.com/andrea-magni/TFrameStand which have dialog box samples.

... or less, it depends on the subjects

Drawing forms according to screen size is a nice feature when targeting a particular device model, but if it's for the general public, don't use it. FMX uses the source screen with the same width/height for a specified OS. Just 2 pixels wider and it returns to the default view (according to tests I did a long time ago). It's preferable to draw our screens using the numerous layouts (grid, flow, layout) and alignments. Think responsive, like for a web page. If you draw your screen by pixel, use a TScaleLayout as a global container. It has a virtual size and a real size. You can use it to adapt the size of your content or add a zoom in / zoom out feature. Look a "screens" samples in GetIt to see how Embarcadero suggest to use those features for classic screens in a mobile app.

You submitted an issue. Now it's in the hands of Embarcadero quality team and project managers. Someone will check your issue and try to reproduce it. Depending on the result, it will be opened, closed or they will send you a question about what your case.