Keep a trace of the previous name of a part

Syntax: <OldNameList>
    <OldName>...</OldName>
    ...
</OldNameList>
Default Value: By default the <OldNameList> tag should be absent, which means that the part was never renamed.
Description: This tag is only usefull if you rename a part (change the GIF and XML file names) to still be able to load BBM files that were saved with the previous name.

Since the part numbers which are used in a layout are also listed and saved in the BBM files (the layout file), BlueBrick will not find parts which you have renamed and will display them as a red cross image. To avoid this problem you should add a OldNameList field in the XML file.

Since a part can be renamed several times, you can add all the previous names of the part inside the OldNameList field. This field contains a list of OldName fields the contents of which is the full previous BlueBrick number (part number followed by a dot and by the color number).

Of course you only need to add this field if you have previously published that part on the internet. This is important as people may have created layouts with the previous name of that part. To make their lives easier, you should add the OldNameList field so that they can reload their previous Layout without missing images. If you are just changing the names for personal use, you don't need to keep a full record of the part names.

Note that if you load a layout file with an old name and save it again, the new name will be used during the save. Nevertheless you should never delete a OldNameList field unless you are certaint that all the layout files which were using the old name have been converted. As this feature does not reduce the performance of the BlueBrick software you can leave them forever, just in case.

You can also use the OldNameList field as an alias for the part because actually BlueBrick is treating the previous names as an alias. However, if you add in a new part in the library that has the same name as a previous part that you have renamed, the alias for the renamed part will be ignored. This means, that BlueBrick only creates the alias if there is not another part with the same name.