Issue link: https://resources.pcb.cadence.com/i/1180190
Migration Guide for Allegro Platform Products Core Allegro Platform Back-End Products October 2019 68 Product Version 17.4-2019 © 1999-2019 All Rights Reserved. The amount by which you can reduce the group's size, will vary by the fields and types of elements inside of the group. In some cases, you may be able to reduce by almost ½, while in others, no adjustment may be necessary. This is one of the situations where you may need a few tries to get the ideal size. Form Resizes when Changing Between Active Tabs and Wizard Pages If your form has a tab set (or is a multi-page wizard), with different tabs having significantly different amounts of content, then you may notice that the form changes size as you move between tabs or pages. The form will only ever expand. If you move from a larger page to a smaller, less densely populated form, the size of the larger tab is retained. This can be both a blessing and a curse. If the larger tabs are rarely used, then having a large UI just in case the user happens to move to that tab is unnecessary. However, if the tabs are all typically used in the flow of using your command, then having the form resize as it is progressed through may be considered annoying. In the latter case, add the FLEXMODE FIXEDSIZE tag to your form file, and update the form's PORT statement with the desired size to be used regardless of which tab / page is active. If all fields do not fit on the form at the give PORT line's size, then fields (usually the OK, Cancel, and Help buttons at the bottom) may go off the edge of the form and will not be visible for user interaction. Because of this, caution and testing is needed when using this option. Note that you can always use these three buttons by typing done or cancel on the command line, or by pressing the F1 key for context-sensitive help. Form Sizes – Default Sizes In past releases, the form size (assuming a non-resizable form) was based upon the principle of "shrink wrapping" to the fields defined in the form file. This means that the form's size is based on the maximum row + width and column + height for any fields in the form. The total size of the form would be increased to compensate for the status line on the bottom plus any icons needed in the top title bar. With 17.4-2019, a similar process is performed. However, due to spacing calculation differences, field size differences (seeButton Field Sizes entry), number of items displayed in a list in the same vertical space, and similar items, you may find that you need to make your form bigger or smaller. To accommodate these changes, update the XY placement of individual fields and/or their FSIZE entries. As a rule, fields should be placed two rows apart if they are simple, one-line fields (string fill-ins, text labels, check boxes, etc). If the first field is at row 5, then the next lines should be at rows 7, 9, etc.