There are two ways to change and update a component after it has been created.
The first way is to simply use the component in an application, make the modifications that you want and then to save the component back as a new component, potentially overwriting the previous file. This is the same process used to create the initial component, the only difference being that you started the process by using a component to seed the initial functionality and behavior. This technique is most applicable when you want to introduce significant structural change to a component, for example adding or removing controls, render extensions or actions. In these situations the component you are creating is not really related any longer to any instances that they user may have created and would be difficult to synchronize while guaranteeing compatible behavior.
The second approach for updating a component is most suitable when you want to make
cosmetic changes to the component and have those changes be applicable to any of the current
instances of the component in the application. In this case you can edit the component file
directly from the templates directory launching a . When you do this, the component
will automatically be opened and applied to a sandboxed Storyboard project containing a single
screen and single layer. From within this sandboxed project, you can change the existing properties
such as color, images or variable values. When the component is edited in this fashion, it will save a
history of what properties have been changed along with a new internal revision number.
When components are changed using the technique the changes that are recorded within the template can be applied to components that have been used in the current application. From the select the component to update and right click and select the option. This selection will scan the application for any uses of the component that are not already synchronized with the latest changes in the template and offer to synchronize the changes for you.