Axure Docs
  • Axure RP Reference
  • Axure RP Tutorials
  • Axure Cloud Reference
  • Support
  • Download

›Components

Installing and Activating RP

  • Activating Axure RP 10
  • Installing on macOS
  • Installing on Windows
  • Axure License Portal

Getting Started

  • Getting Started Video
  • The Axure RP Environment
  • Viewing and Sharing Your Prototypes
  • Keyboard Shortcuts
  • Auto-Saved Backup Files

Working with Widgets

  • Organizing Widgets
  • Widget Groups
  • Styling Widgets
  • Widget Libraries
  • The Grid, Guides, and Snapping

Basic Widgets

  • Buttons, Shapes, & Text
  • Images
  • Hot Spots
  • Lines & Arrows
  • Dynamic Panels
  • Inline Frames
  • Text Fields & Text Areas
  • Droplists
  • List Boxes
  • Checkboxes
  • Radio Buttons
  • Trees
  • Tables
  • Classic Menus
  • Snapshots

Working with Pages

  • Managing Pages
  • Styling Pages

Components

  • Creating and Using Components
  • Component Views
  • Raised Events

Introduction to Interactions

  • Events, Cases, and Actions
  • List of Events
  • List of Actions
  • Text Links
  • Style Effects
  • Animations

Advanced Interactions

  • Variables
  • Conditional Logic
  • Math, Functions, and Expressions
  • Selection Groups
  • Move Action Boundaries

The Repeater

  • Repeaters
  • Dynamically Adding Rows
  • Dynamically Deleting Rows
  • Updating Rows
  • Marking Rows
  • Sorting Rows
  • Filtering Rows
  • Pagination

Adaptive Views

  • Adaptive Views

Documenting Your Prototype

  • Page and Widget Notes
  • The Word Specification
  • Printing

Flow Diagrams

  • Flow Diagrams
  • Flow Connectors

Publishing Your Prototype

  • The Prototype Player
  • Customizing the HTML Output
  • Web Fonts and Font Mapping

Team Projects

  • Team Projects Overview
  • Creating and Sharing Projects
  • Working with Team Projects
  • Team Project History
  • Troubleshooting Team Projects
  • Upgrading RP 9 Team Projects to RP 10
  • Upgrading RP 8 Projects to RP 10

Component Views

Component views are alternate versions of components designed for specific contexts. They allow you to create a component once and then rearrange, resize, and restyle its widgets to fit each context you intend to use it in. When you add an instance of a component to the canvas, you can choose which of its views to display.

Adding Views to a Component

To add component views to a component, start by opening the main component on the canvas for editing. Click the canvas to focus the component itself, and then click Add Component Views in the Style pane to open the Component Views dialog, where you'll create and manage your views.

To remove component views from a component, click Remove Views at the top-right of the Style pane.

Component View Inheritance

Component views are organized into chains of inheritance. The first link in the chain, the view from which all others inherit, is the Base view. Each view you add inherits its widgets and widget properties either directly from the Base view or from another view in the chain.

For example, the chain of inheritance for a button component might looks like this:

Primary Button (Base) > Secondary Button > Text Link Button

  • Edits made in the Primary Button view would be reflected in both the Secondary Button and Text Link Button views as well.

  • Edits made in the Secondary Button view would be reflected in the Text Link Button view but not in the Primary Button view.

  • Edits made in the Text Link Button view would only affect that view.

Editing Diagrams in Component Views

Once you've added component views to a component, you can access each view by clicking its name at the top of the canvas. The color of a view's name indicates whether or not it will be affected by edits you make on the canvas:

  • Dark Blue: The view currently displayed on the canvas. Edits will affect this view.
  • Light Blue: The Affect All Views checkbox is checked. Edits will affect all views.
  • Grey: The Affect All Views checkbox is unchecked. Edits will not affect all views.

Furthermore, if you edit a widget property in a child view, edits to the same property in a parent view will no longer affect the child view. For example, if you change a button's fill color to pink in a child view and then change that same button's fill color to green in the parent view, the button will still be pink in the child view, not green.

Tip

To take full advantage of the benefits of component view edit inheritance, we suggest you take a top-down approach to editing your diagrams, starting in the Base view and then working your way down the chain.

Cross-View Widget Properties

You can change the visual styling, size, and position of widgets freely across component views. Some widget properties, however, are always the same in every view. These include widget text, notes, and interactions/interactive properties. Making edits to these on a widget in one view will always affect all other views as well.

Additionally, special widget properties like the options in a droplist widget, the rows and columns in a table widget, and the nodes in a tree widget, are also shared across views.

If you need a cross-view widget property to vary across your component views, create an additional copy of the widget for each variation and use the "unplace" feature to choose which version of the widget appears in each view.

Unplaced Widgets

"Unplaced" widgets are widgets that are included in some of a component's views but not in others. Any widgets that have been unplaced from the current view are listed in orange in the Outline pane.

Note

To ensure that you see both placed and unplaced widgets in the Outline pane, click the Sort and Filter icon at the top-right of the pane and select Placed or Unplaced.

There are two ways to unplace a widget from a view:

  • You can unplace a widget from the current view and its children by right-clicking the widget and selecting Unplace from View. You can also do this by selecting the widget and pressing DELETE.

  • If you add a new widget to a child view, the widget will be automatically unplaced from all parent views (unless Affect All Views is checked).

    Warning

    If you DELETE a widget from the base view or while Affect All Views is checked, the widget will not be unplaced; instead, it will be deleted from all views.

You can place an unplaced widget in the current view and its children by right-clicking it and selecting Place in View.

To delete a widget from all views entirely, right-click it and select Delete from All Views. This will completely remove the widget from the component instead of just unplacing it.

Choosing a Component View on the Canvas

When you add a component instance to the canvas, use the Component Views dropdown in the Style pane to choose which of its views to display.

Component Views and Adaptive Views

You can set up your component views to work in conjunction with your adaptive view sets. Make sure that your component views have the same names and inheritance structure as your adaptive views, and your component views will switch automatically in the browser along with your adaptive views.

← Creating and Using ComponentsRaised Events →
  • Adding Views to a Component
  • Component View Inheritance
  • Editing Diagrams in Component Views
    • Cross-View Widget Properties
    • Unplaced Widgets
  • Choosing a Component View on the Canvas
    • Component Views and Adaptive Views
Axure Docs
Stay Connected

Sign up to receive Axure tutorials and news. You can unsubscribe at any time.

Axure
Axure RP 10Axure CloudEnterpriseCompanyDownloadPurchase
Legal
Customer AgreementPrivacy PolicyGDPRSecurityPatents
Resources
BlogForumLicense Portal
Support
Learn and SupportGetting StartedReferenceWidget LibrariesAxure RP 9 Documentation and Tutorials
Copyright © 2002–2023 Axure Software Solutions, Inc. All rights reserved. Axure® is a registered trademark of Axure Software Solutions, Inc.