Skip to main content
ptc-2870287-Bedrock
7-Bedrock
April 24, 2014
Solved

Axis Display and Csys display on Creo 2.0 M100 is grayed out !

  • April 24, 2014
  • 8 replies
  • 7630 views

We have just upgraded to Creo 2.0 M100 and the 2 display options "Axis Display" and Csys Display are grayed out , why? how to correct?


This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.
Best answer by Mahesh_Sharma

Robert,

This is because of change in functionality from M100 datecode. If display of planes or axis is set to no in config.sup, options will inactive in interface. Remove/Comment config options display_coord_sys and display_axes from config.sup to enable in interface.

8 replies

Mahesh_Sharma
Mahesh_Sharma22-Sapphire IAnswer
22-Sapphire I
April 24, 2014

Robert,

This is because of change in functionality from M100 datecode. If display of planes or axis is set to no in config.sup, options will inactive in interface. Remove/Comment config options display_coord_sys and display_axes from config.sup to enable in interface.

    DHLewis13-Aquamarine
    13-Aquamarine
    April 24, 2014

    Mahesh,

    These display options have always been a preference setting for an organization and a users preferred start environment. They should not have been changed without some way to control this overall action with another config option.

    David

    dschenken1-Visitor
    1-Visitor
    April 25, 2014

    It almost makes sense to change it, if the change is as described. The point of config.sup is to make changes that users cannot override. If there was some reason to never allow access to csys and axis display, then turning it off in the config.sup should do it.

    It's been the case that adding a mapkey to config.sup prevents all other mapkeys from being used, even other mapkeys in the config.sup.

    Simple rule? Don't put things in the config.sup if you expect users to be able to change the status of the options.

    ptc-57674001-Visitor
    1-Visitor
    April 25, 2014

    I am in China, Please modify the system color, that is the path: file/options/system colors/datum

    Terms & ConditionsAccessibility statement