The UI Designer stores the information it uses to generate files in the application.uidesign file and an individually named xxx.uidesign file for each UI Design you create.
As you create objects within your UI Designs and save the associated .uidesign files, the UI Designer generates the code needed to instantiate, display, and respond to events.
The UI Designer follows a well-defined algorithm for creating the generated file's names. This algorithm uses the name of the UI Design plus additional standard terms and file extensions.
The UI Designer code generator adheres to best programming practices for creating S60 and UIQ code and supporting files. You can expect the generated code to appear in the same place within the generated files that a typical developer would place it if he/she were creating the associated files manually.
Example for S60:
If your application is named MyProgram, the associated application level generated files would be named:
If your application contains a UI Design named MyDesign, the associated generated files would be named:
In addition, the following resource files may also be generated:
Example for UIQ:
If your application is named MyProject (Multipage type) the associated application level generated files would be named:
If your application contains a UI Design named MyDesign, the associated generated files would be named:
In addition, the following resource files may also be generated:
Use the standard Carbide.c++ editing protocols to examine the contents of any of these files. Before editing their content, be aware of the restrictions that apply and possible side-effect that can occur if you modify any generated files.