repetitively clicking on the chosen component in the component palette actually inserts the component several times, however, this "bug" occurs (TabOrder's counter doesn't change and all components are linked to each other)... so if you delete one button, all others that were added after the button you want to delete will also be deleted...
Thanks Embarcadero... always a new emotion in every issue!
----------------------------------------------
The higher the degree, the greater the respect given to the humblest!RAD 11.3
Dont forget... in FMX any component can be a "container" for another components...
Then, of course, clicking many times to add many buttons on form, you are just "add" a button into another button.... in chain (or would in "blockchain" :)))))
that way, if a butotn have many others buttons, then, if you delete a first button, you will go delete all component that is contained into it.
Button1[ Button2 [ Button3[ Button4.... ] ] ] ]
CONFIRMED... THE BUG WAS (IN FACT) THE PROGRAMMER CLICKING AND DONT PAYING ATTENTION WHERE HE CLICKED :))))
----------------------------------------------
The higher the degree, the greater the respect given to the humblest!RAD 11.3
Look, the FireMonkey (FMX) is another framework with another way to see the things... it is based on display performance and way... DirectX, GPIPlus concepts...
As MSWindows is distinct from Linux, macOS O.S., Mobiles, etc...
Then, changes your "mind" about programming!
Each platform (32, 64, 128, etc... bits) will be distincts. Each operating system, too!
In the middle, you will have many ways (frameworks) to 'join" or "to do the conversation more easy"...
OK! VCL is not FMX, but you can use it togheter in some moments, because the RTL does the "bridge" into it. But it's not so easy or avaliable all time.
It's necessary knowledge and experience by years to domain it.
sorry, i'm not expert at all.
----------------------------------------------
The higher the degree, the greater the respect given to the humblest!RAD 11.3
Anyway, the concept of "container" for FireMonkey is as explained above. Any component, or almost all that I know of, can be a "container" for other components.
This is "object-oriented programming" literally, that is, classes that receive other classes implementing "composition", and forming a new component for the programmer to use in the best possible way in his project.
A flexibility that the VCL framework lacks, for example, as it was a project with roots in MSWindows and its concepts of visual inheritance, because at that time it made sense.
Today, with the diversity of devices and screens, FireMonkey has a better position in many graphic appeal projects. However, both have their place in the sun
----------------------------------------------
The higher the degree, the greater the respect given to the humblest!RAD 11.3