> ugh. Where did you take this from?

 From the hints that they would be surfaced as FMX components, and that 
it's what the old VGScene component for that or "NakeyMonkey" do.


If you want to make native controls part of the FMX scene graph, ie. 
allow them to be rotated or overlayed by other FMX components f.i., it 
means they have to be rendered as textures, which in turns drastically 
reduces your implementation options.


If you don't place them in the scene graph, then it means native 
components would appear in front of any other FMX component, since FMX 
is basically just a bunch of vector components rendering to a single 
native component (a DirectX or OpenGL viewport). But that wouldn't be 
very clean as the native components could then lag or head other updates 
in the FMX viewport.


This is different from the VCL, where components are native components 
that may hold visual subcomponents (TGraphicControl), and where that 
allows to mix-n-match more freely between native and non-native 
components, without compromising the native components.


Eric