Inheritance diagram for oaObserver<oaTech>:
Public Methods | |
oaObserver (oaUInt4 priorityIn) | |
virtual | ~oaObserver () |
virtual void | onCreate (oaTech *tech) |
virtual void | onFirstOpen (oaTech *tech) |
virtual void | onPurge (oaTech *tech) |
virtual void | onPreReopen (oaTech *tech, oaChar newMode) |
virtual void | onPostReopen (oaTech *tech, oaChar oldMode) |
virtual void | onTruncate (oaTech *tech) |
virtual void | onPreSave (oaTech *tech) |
virtual void | onPostSave (oaTech *tech, oaBoolean succeeded) |
virtual void | onPreSaveAs (oaTech *tech) |
virtual void | onPostSaveAs (oaTech *tech, oaBoolean succeeded) |
virtual void | onPreModify (oaTech *tech, oaTechModTypeEnum modType) |
virtual void | onPostModify (oaTech *tech, oaTechModTypeEnum modType) |
virtual void | onConflict (oaTech *mostDerivedTech, oaTechConflictTypeEnum conflictType, oaObjectArray conflictingObjs) |
virtual void | onUnboundRef (oaTech *tech, oaTechHeader *header) |
virtual void | onClearanceMeasureConflict (oaTechArray conflictingTechs) |
virtual void | onDefaultManufacturingGridConflict (oaTechArray conflictingTechs) |
virtual void | onGateGroundedConflict (oaTechArray conflictingTechs) |
virtual void | onDBUPerUUConflict (oaTechArray conflictingTechs, oaViewType *viewType) |
virtual void | onUserUnitsConflict (oaTechArray conflictingTechs, oaViewType *viewType) |
virtual void | onPreOpenRefs (oaTech *tech) |
virtual void | onPostOpenRefs (oaTech *tech) |
virtual void | onPreAttach (oaLib *lib, const oaScalarName &attachLibName) |
virtual void | onPostAttach (oaLib *lib, const oaScalarName &attachLibName) |
virtual void | onPreDetach (oaLib *lib) |
virtual void | onPostDetach (oaLib *lib) |
oaObserver (oaUInt4 priorityIn, oaBoolean enabledIn) | |
virtual void | onProcessFamilyConflict (const oaTechArray &conflictedTechs) |
virtual void | onExcludedLayerConflict (oaTech *mostDerivedTech, const oaPhysicalLayer *excludingLayer, const oaLayer *excludedLayer) |
See oaObserver for information on using Open Access observer template classes to derive and instantiate observers in an application.
|
This is the oaObserver<oaTech> constructor. If multiple observers exist for a given oaTech notification event, observers with a lower priorityIn value are called before those with a higher value.
|
|
This is the destructor for the oaObserver<oaTech> class. This function destroys this oaObserver<oaTech> object, deactivating and deleting this observer from the Tech observer list, and freeing all resources associated with this observer. |
|
|
|
This function is called when the ClearanceMeasure attribute has conflicting (non-equal) values in a graph of technology databases. This can occur when a tech database that is part of a graph of referenced techs is edited out of context and then reintroduced into the graph. The application's derived class should implement this function to receive notification when a tech database has an ClearanceMeasure attribute whose value conflicts with another ClearanceMeasure attribute in a different tech in the graph of tech databases. Refer to Incremental Technology Databases in the Using Technology Databases section of the Programmers Guide for more information about referenced tech databases.
|
|
This function is called when there are conflicting technology objects in a graph of technology databases. This can occur when a tech database that is part of a graph of referenced techs is edited out of context and then reintroduced into the graph through reopening the graph. The application's derived class should implement this function to receive notification when there is a conflicting technology object in the graph of tech databases. Note: It is the application's responsibility to resolve the observed conflict. The observed conflict is resolved when all except one object in the conflictingObjs array are deleted. Refer to Resolving Conflicts (Due to Out-of-Context Edits) in the Using Technology Databases section of the Programmers Guide for more information.
|
|
This function is called after an oaTech object is created. The application's derived observer class should implement this function to receive notification when an oaTech object is created.
|
|
This function is called when the DBUPerUU attribute has conflicting (non-equal) values in a graph of technology databases. This can occur when a tech database that is part of a graph of referenced techs is edited out of context and then reintroduced into the graph. The application's derived class should implement this function to receive notification when a tech database has a DBUPerUU attribute whose value conflicts with another DBUPerUU attribute in a different tech in the graph of tech databases. Refer to Incremental Technology Databases in the Using Technology Databases section of the Programmers Guide for more information about referenced tech databases.
|
|
This function is called when the DefaultManufacturingGrid attribute has conflicting (non-equal) values in a graph of technology databases. This can occur when a tech database that is part of a graph of referenced techs is edited out of context and then reintroduced into the graph. The application's derived class should implement this function to receive notification when a tech database has a DefaultManufacturingGrid attribute whose value conflicts with another DefaultManufacturingGrid attribute in a different tech in the graph of tech databases. Refer to Incremental Technology Databases in the Using Technology Databases section of the Programmers Guide for more information about referenced tech databases.
|
|
This observer notification is triggered when an excluded layer is detected in the ITDB graph, which is rooted at the mostDerivedTech.
|
|
This function is called when an oaTech object is first opened. The application's derived class should implement this function to receive notification when an oaTech object has been opened.
|
|
This function is called when the GateGrounded attribute has conflicting (non-equal) values in a graph of technology databases. This can occur when a tech database that is part of a graph of referenced techs is edited out of context and then reintroduced into the graph. The application's derived class should implement this function to receive notification when a tech database has a GateGrounded attribute whose value conflicts with another GateGrounded attribute in a different tech in the graph of tech databases. Refer to Incremental Technology Databases in the Using Technology Databases section of the Programmers Guide for more information about referenced tech databases.
|
|
This function is called after before a technology library attachment is made using oaTech::attach.
|
|
This function is called just after a library attachment is removed using oaTech::detach.
|
|
This function is called after an oaTech object has been modified. The application's derived class should implement this function to receive notification when an oaTech object has been modified.
|
|
This function is called after references are bound for an incremental technology database. These notifications occur after a technology database that has references is opened, and also after oaTech::setRefs() is performed on a technology database. The application's derived class should implement this function to receive notification after the binding and opening of referenced databases. Note: There is a notion here of a recursive descent. For example, when you have a technology database graph, A->B->C, if you open A, and B and C are not opened, you get the following notifications:
|
|
This function is called just after an oaTech object is reopened using a new access mode. The application's derived class should implement this function to receive notification when an oaTech object has been reopened in a new access mode.
|
|
This function is called just after an attempt to save an oaTech object to disk. The application's derived class should implement this function to receive notification when a save on an oaTech has been attempted.
|
|
This function is called after an attempt has been made to save an oaTech to disk in a user-specified library (through an oaTech::saveAs call). The application's derived class should implement this function to receive notification when an attempt has been made to save an oaTech object to disk in a user-specified library.
|
|
This function is called just before a technology library attachment is made using oaTech::attach.
|
|
This function is called just before a library attachment is removed using oaTech::detach.
|
|
This function is called before an oaTech object is modified. The application's derived class should implement this function to receive notification when an oaTech object is about to be modified.
|
|
This function is called before references are bound for an incremental technology database. These notifications occur when a technology database that has references is opened, and also when oaTech::setRefs() is performed on a technology database. The reference is opened and the referenced databases are bound. Referenced databases may themselves be opened in order to complete the binding. The application's derived class should implement this function to receive notification prior to the binding and opening of referenced databases. Note: There is a notion here of a recursive descent. For example, when you have a technology database graph, A->B->C, if you open A, and B and C are not opened, you get the following notifications:
|
|
This function is called before an oaTech object is reopened using a different access mode. The application's derived class should implement this function to receive notification when an oaTech object is about to be reopened.
|
|
This function is called just before an oaTech object is saved to disk. The application's derived class should implement this function to receive notification when an oaTech object is about to be saved.
|
|
This function is called just before a design is saved to disk in a user-specified library (through an oaTech::saveAs call). The application's derived class should implement this function to receive notification when an oaTech object is about to be saved in a user-specified library.
|
|
This function is called when the ProcessFamily attribute has conflicting (non-equal) values in a graph of technology databases. For the ProcessFamily attribute, note that the empty string (“”), is interpreted to mean that the attribute value is unset. An unset attribute does not conflict with other attribute values. A ProcessFamily conflict can occur when a tech database that is part of a graph of referenced techs is edited out of context and then reintroduced into the graph. The application's derived class should implement this function to receive notification when a tech database has a ProcessFamily attribute whose value conflicts with another ProcessFamily attribute in a different tech in the graph of tech databases. Refer to Incremental Technology Databases in the Using Technology Databases section of the Programmers Guide for more information about referenced tech databases.
|
|
This function is called when an oaTech object is about to be purged from memory. The application's derived class should implement this function to receive notification when an oaTech object is about to be purged.
|
|
This function is called just before an oaTech is truncated (for example, after all contents are removed). The application's derived class should implement this function to receive notification when an oaTech object is about to be truncated.
|
|
This function is called when an unbound reference to a technology database in the graph of referenced tech databases is detected when a technology database graph is opened using oaTech::open(). (This can occur when a referenced tech database is unavailable.) The application's derived class should implement this function to receive notification when there is an unbound reference to a tech database. Refer to Incremental Technology Databases in the Using Technology Databases section of the Programmers Guide for more information about referenced tech databases.
|
|
This function is called when the UserUnits attribute has conflicting (non-equal) values in a graph of technology databases. This can occur when a tech database that is part of a graph of referenced techs is edited out of context and then reintroduced into the graph. The application's derived class should implement this function to receive notification when a tech database has a UserUnits attribute whose value conflicts with another UserUnits attribute in a different tech in the graph of tech databases. Refer to Incremental Technology Databases in the Using Technology Databases section of the Programmers Guide for more information about referenced tech databases.
|
Copyright © 2002 - 2010 Cadence Design Systems, Inc.
All Rights Reserved.