Posted by jpluimers on 2019/12/19
On G+, Tom Field bumped in the [WayBack] issue that the IDE would add VCL units to the uses list when putting FMX controls on a form.
I’ve observed it the other way around as well, and there are two things you need to check:
FrameworkType element in your .dproj file
VCL or FMX values are allowed, but in the past more values were used, see Delphi .dproj files: FrameworkType and FormType.{$R *.dfm} for VCL or {$R *.fmx} for FMX.References:
{$R *.fmx}or{$R *.dfm}in the unit. You may be able to get away with renaming the.dfmfile to.fmx,and changing the directive in the unit..dprojfile tells you what kind of application it is (FMX or VCL) in theFrameworkTypeelement and the IDE should respond to that correctly.
–jeroen
Source: [WayBack] In the Berlin Update 2 IDE. I’m working on a multi-device app I’m creating. …
The Wiert Corner - irregular stream of stuff 
Tom Field said
My fleeting 15 minutes of fame have now fled! Thanks for the memory. Tom Field. PS I’m still doing VCL/FMX development and loving the results. http://www.rspec-astro.com and http://www.fieldtestedsystems.com
jpluimers said
How cool is that!
Note that your fame is still archived in the WayBack link of the post. I try to archive most of the links before posting the blog article. Link rot and killing of services is all too common nowadays.
xepol said
It would be better if they could just use non conflicting resources (mainly cursors I found).
Otherwise, if you are sticking to wintel land, fmx and vcl can play together in the same app.