Moreover, there are several new releases of Delphi these days, it may be useful to just take a project that is "several" Delphi, released by the old ones and recreating the * .dproj file. There are so many projects in the dproj file now that inexplicable behavior, especially with mobile targets, can often be cured by “starting over”. In principle, this is quite simple - create a new "empty" project of the type you want (VCL project or Multi-device), and then add the old files by dragging them to the new project in the project tree. This works great for regular units and forms, but seems to crash with frames because the project does not recognize dropped frames the same way you would if you used "New ... Delphi..Frame" in the IDE. Exactly since EMB introduced FireMonkey, I think there are fixes. My question is the easiest way to get around this "frame blindness." These solutions seem to work (but are confusing):
- In the new project, create the "New" "Frame" as intended and rename it to the existing "old" file. Delete a new empty frame from the disk and replace it with the old file (changing the name if necessary). Messy - it's easy to forget to save the component name in the track.
- Drag and drop personnel units in normal mode, they will be processed as forms, and you will get errors from the forms that require these frames. Close the project, then manually edit the dproj file using the sentence here
changes:
<DCCReference Include="x\y\z\myFrame.pas"> <Form>frameMy</Form> <DesignClass>TFrame</DesignClass> </DCCReference>
in
<DCCReference Include="x\y\z\myFrame.pas"> <Form>frameMy</Form> **<FormType>dfm</FormType>** <DesignClass>TFrame</DesignClass> </DCCReference>
Does anyone have a better solution? Did I miss something?
source share