Your previous menu customization data is stored in a MNS/MNU, CUI, or CUIx file.
You can migrate your menu customization to the new release using the Migrate Custom
Settings utility or the Transfer tab of the CUI Editor.

Commands are created and managed through the Command List pane on the Customize tab
of the CUI Editor. Once the command has been created, it can be added to different
user interface elements.

For example, to add a command to a ribbon panel, expand the Ribbon and Ribbon Panels
node in the Customizations In <file name pane, and then the ribbon panel you want to modify. Drag the command from the Command
list to the ribbon panel you want to add it to.

The PICKFIRST and DBLCLKEDIT system variables both need to be set to 1 to enable double-click
editing.

This happens when the workspace to which you made changes is not the current workspace.
To see the changes, set the modified workspace current.

An enterprise CUIx file can only be edited when it is loaded as the main CUIx file
or as a partial CUIx file to the main CUIx file. It is recommended that you load the
file as the main CUIx file when you need to make edits. If you create a workspace
that needs to include user interface elements from the CUIx file that is normally
designated as the main CUIx file, load the main CUIx file temporarily as the enterprise
CUIx file while making edits.

Workspaces are used to control the display of pull-down menus on the menu bar.

Workspaces are used to control the positioning of pull-down menus on the menu bar.

The display of the menu bar can be changed using the MENUBAR system variable. Set
the MENUBAR system variable to 1 to display the menu bar.

This is most commonly due to the way toolbars are loaded at startup when a combination
of main, enterprise, and partial CUIx files are used. Use the /w command line switch
as part of your Windows Desktop shortcut. This causes the program to reload the workspace
upon startup and place the toolbars in their correct locations.

This happens because the images for the custom icons used by the user interface elements
are not located in the program’s Support File Search Paths. Locate the missing images
using Windows Explorer or File Explorer, and copy them to the location defined under
the Customization Files Custom Icon Location node on the Files tab of the Options dialog box. By default,
the path under the Custom Icon Location node is

• <drive:Users<user profile nameAppDataAutodesk<product name<release number<languageSupportIcons

A flyout might not work for correctly because

• No commands have been assigned to the toolbar that is referenced.
• A control is part of the toolbar that is referenced.
• The referenced toolbar was removed from the CUIx file, or the alias assigned to the
  toolbar was changed.

The message box is displayed when a toolbar that is being referenced as a toolbar
flyout cannot be found. Verify that all necessary CUIx files are loaded, and the alias
assigned to the flyout matches the toolbar in the CUIx file. To resolve the problem,
perform the following steps:

1. Launch the CUI Editor and select the flyout on the toolbar that is not working properly.
2. In the Properties pane, review the value of the Source Toolbar property.

   Use the Find option to look for a toolbar element with an alias that matches the text
   string in the Source Toolbar property of the flyout that does not work. If one is
   not located, remove the flyout from the toolbar, and drag the toolbar that you want
   to reference as a flyout onto the toolbar.

3. Close the CUI Editor and test the flyout to verify the problem has been resolved.