Echelon NodeBuilder Resource Editor - Manual (Page 72)

reflected in your new profile. See Creating and Editing a Functional Profile for more
information.
Removing and Obsoleting Resources
Resources may reference other resources in the same resource file set or other resource
file sets, so deleting a resource could impact other resources, even in resource file sets
that you may no longer have loaded on your computer. Applications can also reference
resources, and it is important that an invalid resource not be passed to an application
because the original resource was replaced by another. To help prevent references to
non-existent resources or invalid resources (due to reuse of a deleted index), the resource
editor does not allow you to delete an individual resource. It instead provides two
alternatives: you can either mark a resource as deleted (and optionally later purge it
from the resource file), or mark it as obsolete.
During development, you can delete resources that you have defined, but not yet released
to production. To mark a resource as deleted, right-click it and then click Remove on
the shortcut menu. Alternatively, you can select the resource and then press DEL. This
does not physically delete the resource from the resource file. Instead, a tilde (“~”)
character is appended to the name to indicate that the resource has been removed. By
default, the resource editor does not display resources with a tilde as the last character,
so the resource will appear to be deleted. You can see any resources that you have
removed by opening the View menu, clicking Options, and then setting Show
Removed Resource Items. You can undelete a removed resource by first showing
removed resource items, and then deleting the tilde from the resource name. To remove
a deleted resource, you can purge removed resources from the resource file set as
described in Purging a Resource File Set, later in this chapter.
You should not delete any resources that you have released to production. You may have
users that have created devices based on those resources, created resource files that
reference those resources, or created applications that use those resources. However, you
may decide that a resource that you have created should no longer be used for new
designs, even if it is used in existing designs. In this case you can mark the resource as
obsolete. This tells your users that they should no longer use the resource in new
designs, but allows the resource to continue to be used in existing designs. For example,
the SNVT_lev_disc type is marked as obsolete in the standard resource file set because it
has been replaced by SNVT_switch. The SNVT_lev_disc type continues to be used in
many devices, but newly designed devices should use SNVT_switch instead.
To mark a resource as obsolete, double-click the resource and then set Mark this Item
Obsolete. You can specify whether you want to see obsolete resources by opening the
View menu, clicking Options, and then setting or clearing Show Obsolete Resource
Items. You can remove the obsolete flag from a resource by clearing Mark this Item
Obsolete for the resource.
Purging a Resource File Set
You can purge a resource file set. When you delete a resource in the Resource Editor, it is
marked as deleted, but it is still physically in the resource file. This helps prevent
serious problems that could occur if you had other resources referencing the deleted
resource. This is most important once you have started shipping a device. You should
never delete resources used by devices in the field, though you can mark them as
obsolete. However, during development, you may create resources that you decide never
to ship. In this case, you may prefer that these deleted resources not remain in your
resource file. In this case, you can purge the resource file. Purging physically removes
64 Creating and Modifying Resources