|
Size: 864
Comment:
|
Size: 2018
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 5: | Line 5: |
| Application form designed with Qt '''designer''' tool | Application form designed with Qt '''designer''' tool. Because we are using different versions of Qt on win32 and X11, all changes to form should be made on X11. |
| Line 7: | Line 7: |
| There are few custom edit widget, if field is string we should use CCDDTextEdit widget. All input widget that we should use listed in left part of designer under Input tab and have a prefix CC. | On win32 we are only compiling cpp files generated on X11 platform. |
| Line 9: | Line 9: |
| Each edit widget name should be the same as field name in corresponding datadictionary, for example sstock.coment edit widget should have name coment. | There are few custom edit widget e.g. if field is string we should use CCDDTextEdit widget. All input widget that we should use listed in left part of designer under Input tab and have a prefix CC. === Widget naming === *Each edit '''widget name''' should be the same as '''field name''' in corresponding datadictionary, for example sstock.coment edit widget should have name coment. *There is '''fieldPath''' property for this widget. If it is empty, main aad structure will be used (fdb[0]), e.g. STOCK for staad. If field is part of another structure, fieldPath shoul be set to corresponding dataset name e.g. for all BOM fields on staad/component page this field should be BOMCMP. Name of dataset can be found in '''static char * mytypes[]''' defined in main_window.ui.h '''(NOTE this array MUST be synchronized with fdb[] because it is only link between xxaad and application)''' *All structures are flat, so there is no srec and vrec. *If field is array e.g. '''price[0]''' in stock, widget should have a name like '''price_0_ARRAY''' *If field are not unique in widget it should have prefix like STOCK__code *If there are member of substructure like supp in stock, it will be supp_0_STRUCTARR for sstock.ssupp[0]supp *all of the above implemnted and documented in ccabstract_data.h |
| Line 12: | Line 22: |
Because we are using different versions of Qt on win32 and X11, all changes to form should be made on X11. |
=== Compiling aad === |
| Line 16: | Line 25: |
gui/build.ksh on win32 should always run after gui build on X11 |
Located in CCDIR/std/gui dir.
Each application has its own subdirectory with its own main (main.cpp), main_window.ui XML form description, main_window.ui.h with slots, project file xxaad.pro, most of them has ccddfunc_imp_***.(h | cpp) with special functions
Application form designed with Qt designer tool. Because we are using different versions of Qt on win32 and X11, all changes to form should be made on X11.
On win32 we are only compiling cpp files generated on X11 platform.
There are few custom edit widget e.g. if field is string we should use CCDDTextEdit widget. All input widget that we should use listed in left part of designer under Input tab and have a prefix CC.
Widget naming
Each edit widget name should be the same as field name in corresponding datadictionary, for example sstock.coment edit widget should have name coment.
There is fieldPath property for this widget. If it is empty, main aad structure will be used (fdb[0]), e.g. STOCK for staad. If field is part of another structure, fieldPath shoul be set to corresponding dataset name e.g. for all BOM fields on staad/component page this field should be BOMCMP. Name of dataset can be found in static char * mytypes[] defined in main_window.ui.h
(NOTE this array MUST be synchronized with fdb[] because it is only link between xxaad and application)
- All structures are flat, so there is no srec and vrec.
If field is array e.g. price[0] in stock, widget should have a name like price_0_ARRAY
If field are not unique in widget it should have prefix like STOCKcode
- If there are member of substructure like supp in stock, it will be supp_0_STRUCTARR for sstock.ssupp[0]supp
- all of the above implemnted and documented in ccabstract_data.h
Compiling aad
On win32 we are only compiling cpp files generated on X11 platform.
gui/build.ksh on win32 should always run after gui build on X11