Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Determining where a mixin is referenced

Updated on April 5, 2022

Determining where a mixin is referenced

To preview the mixin in use by the mixins and components that reference it, select a component from the Preview with list on the right. This list displays all the components that reference the selected mixin.

After selecting a component in which to preview the mixin, click Details to view a summary of where the mixin is used within the component styles.

If you upgraded a skin rule from PRPC Version 5.X through PRPC Version 6.2 SP2, the Standard Active, Standard Inactive, Sub Active, and Sub Inactive mixins are populated with the values from your Quick Create settings.

  • Skin rules

    Use the skin to specify the presentation of your content. You can style all presentation elements of your interface in the skin, including typography, borders, backgrounds, layouts, and UI placement and alignment. By defining presentation attributes in the skin, you separate the content that is defined in sections and harnesses from its presentati

  • About mixins

    Use the Mixins tab to define mixins. A mixin is a reusable style pattern.

  • Defining a new mixin

    To create a new mixin, click Add. The mixin is populated with default values.

  • Deleting a mixin

    You cannot delete a mixin if another mixin or component inherits styles from that mixin. Mixins and components that reference the selected mixin display in the Preview with list on the right.

  • Skin rules - Renaming a mixin

    Renaming a mixin

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us