Issue link: https://resources.pcb.cadence.com/i/1180190
Migration Guide for Allegro Platform Products Core Allegro Platform Back-End Products October 2019 35 Product Version 17.4-2019 © 1999-2019 All Rights Reserved. be set prior to starting the layout editor. ■ Some Windows applications will not respond to Scale and Layout changes made under Display Settings until you sign out. This font scaling will automatically be changed by Windows depending on the display resolution to allow UI text to be more readable. Some scenarios where different resolution and font scaling can lead to incorrect fonts sizes are: ❑ Switching to a different display source when coming out of sleep mode. ❑ Adjusting the Font Scaling without sign out and sign in to Windows. ❑ It is recommended to sign out / in to Windows for the fonts to be sized correctly. ■ The Layout Editor or associated forms displayed in a different resolution or a different font scaling could cause the following issues: ❑ Main menu and right mouse button pop-up menus display at the wrong location, display partially, or not display at all. ❑ Form fonts would be incorrectly sized when displayed on a different monitor than the layout editor UI due to resolution and font scaling differences. ❑ Moving the layout editor to a different monitor than originally started from could show incorrect fonts size. ❑ It is recommended that the layout editor and its associated forms be displayed on monitors of the same resolutions and font scaling to avoid this issue. Setting the resolution and font scaling the same on multiple monitors would resolve the issues. For more display and system related requirements, see Allegro Platform System Requirements. Database ■ 17.2 Compatibility mode is available to maintain 17.2 database format when creating new 17.4 databases or opening 17.2 databases in 17.4. ❑ To enable this mode, set the value of the database_compatibility_mode environment variable, to 17.2. ■ 17.2 Compatibility mode is available for all databases except for APD (.mcm) databases. ■ 17.2 PCB Design Partition (.dpf) databases are not supported in 17.2 Compatibility mode and will be disabled upon opening the database. It is recommended that you import or retract all partitions to the master database and uprev the master to 17.4. ■ Symbol Drawing (.dra) databases will remain in 17.2 database format until new 17.4 functionality is used in the symbol, even if 17.2 Compatibility mode is disabled.