I have the same question as this topic regarding TMSFNCCloudAI (all no visual FNC components ?) and TDataModule.
Why is it not possible to drop a TTMSFNCCloudAI component on a TDataModule in a VCL application?
It seems this limitation is related to the inheritance from TTMSFNCCustomComponent, but could you please clarify the reasoning behind this design decision?
This is a problem for several reasons — for instance, it prevents sharing the same TDataModule between VCL and FMX projects, which is one of the key benefits of using FNC components.
This is not a design decision but a technical limitation. We need to offer functionality for FMX & VCL which are different frameworks, yet you can only register real TComponent descendants once, which means that prior to RAD Studio 11, we could not register non-visual components for both frameworks. With new framework specific defines, this is now possible. We are also working towards a single code base, from now on you will see single units (starting with TMS.). In TMS FNC Core we already have the TTMSFNCDataSet, which can be dropped on a datamodule. We are also going to integrate a TTMSMCPCloudAI component in our MCP distribution which will be droppable on a TDataModule. It's a step by step process.