 |
 |
 |
 |
 |
 |
 |
 |
 |
|
|
|
|
|
|
|
|
|
Inheritance diagram for oaTech:
 |
 |
The oaTech class implements a technology database (oaTech), which contains process information.
A library (oaLib) typically contains a single technology database, and all the designs in the library use that technology database. Alternatively, a user can define an attachment from one library to the technology database in another library. In this case, all the designs in the library use the attached technology database. Whether in the same library or in a different library, the main technology database associated with a design is known as its primary technology database.
Any technology database can contain references to other technology databases. A reference is a mechanism that allows a technology database to inherit information from one or more technology databases. This approach is known as using incremental technology databases.
A referenced technology database can itself reference other technology databases to form a chain, known as a graph of technology databases. All the technology information in a graph is available to the design library. When a design is opened, the primary technology database is opened, and if there are any references, the graph of technology databases is opened as well. For more information, refer to Incremental Technology Databases in the Using Technology Databases section of the Programmers Guide.
When a technology database contained within a library is opened, it is associated with the library and remains the technology database for that library until the database is purged or the library is closed. When a technology database is associated with a library through attachment, an application can remove the association (oaTech::detach) and re-associate the library to another technology database in a different library (oaTech::attach).
The oaTech class can be observed by deriving from oaObserver<oaTech>.
Attached oaTech DatabasesA user can use oaTech::attach to associate a library with a technology database in a different library. In addition, the associations can be made through any number of libraries (using multiple applications of oaTech::attach) as long as the intermediate libraries do not contain technology databases themselves and the final target library does contain a technology database.
Note: To support backward data compatibility, the previous mechanism for attaching technology libraries is still supported. Namely, a string property called techLibName in a library’s oaLibDMData database still specifies the name of the target library. The oaTech::attach function creates the techLibName property when it is called. In order to construct the name of the library, the techLibName string is interpreted in the oaNativeNS namespace.
|
||||||||||||
|
This function creates a technology attachment between the specified library lib and the library with the name attachLibName. If there is an existing attachment, it is first removed. The oacAttachLibraryHasLocalTech error is thrown if a technology database exists locally in the library lib. The oacDMDataCannotGetWriteAccess error is thrown if the library dmData database in the library lib cannot be opened for editing. Note that the library dmData database is needed because this function creates a string property called techLibName in the dmData that specifies the name of the associated technology library.
|
|
|
This function calculates and returns the amount of virtual memory this tech database is currently using. |
|
|
This function decrements the reference count of this tech database by one. If the count reaches zero, this tech database is purged from memory. |
|
|
This function creates the tech database for the specified library. An exception is thrown if the tech database already exists or if the specified library uses an attached tech database in another library.
|
|
|
This function creates the tech database for the specified library. An exception is thrown if the tech database already exists or if the specified library uses an attached tech database in another library.
|
|
||||||||||||
|
This function converts the database units into user units for the specified viewType.
Note: Although users can construct their own oaViewTypes, valid viewTypes for this function are restricted to the set of reserved viewTypes, namely, an oaReservedViewType object constructed with one of the following reserved view type enumerated constants:
The developer can call oaViewType::get(oaReservedViewType) to construct and return a pointer to an a oaViewType object using one of the valid reserved viewType enumerated constants (for example,
|
|
||||||||||||
|
This function converts the database unit area to user unit area for the specified viewType.
Note: Although users can construct their own oaViewTypes, valid viewTypes for this function are restricted to the set of reserved viewTypes, namely, an oaReservedViewType object constructed with one of the following reserved view type enumerated constants:
The developer can call oaViewType::get(oaReservedViewType) to construct and return a pointer to an a oaViewType object using one of the valid reserved viewType enumerated constants (for example,
|
|
||||||||||||
|
This function converts the database unit distance to user unit distance for the specified viewType.
Note: Although users can construct their own oaViewTypes, valid viewTypes for this function are restricted to the set of reserved viewTypes, namely, an oaReservedViewType object constructed with one of the following reserved view type enumerated constants:
The developer can call oaViewType::get(oaReservedViewType) to construct and return a pointer to an a oaViewType object using one of the valid reserved viewType enumerated constants (for example,
|
|
||||||||||||
|
This function attempts to remove the specified oaSaveRecoverType file from disk. It throws an exception if this file cannot be found on disk.
|
|
|
This function attempts to remove the tech database associated with the library specified by lib. The tech database for the library will be removed from disk. If no tech database exists, but the library uses an attached tech database specified with the "techLibName" property, then the attachment property will be removed. It is not an error to remove the tech database even if other libraries use this tech as an attached tech. An exception is thrown if the tech database is open. See the oaTech class description for more information about attached tech databases.
|
|
|
This function attempts to remove the tech database associated with the library specified by libName. The tech database for the library will be removed from disk. If no tech database exists, but the library uses an attached tech database specified with the "techLibName" property, then the attachment property will be removed. It is not an error to remove the oaTech database even if other libraries use this tech database as an attached tech. An exception is thrown if the tech database is open. See the oaTech class description for more information about attached tech databases.
|
|
|
This function removes the technology attachment from the specified library lib. The oacDetachNoAttachment error is thrown if the library does not have a technology attachment to another library. The oacDMDataCannotGetWriteAccess error is thrown if the library dmData database cannot be opened for edit. Note that the library dmData database is needed because the technology attachment information is stored there.
|
|
|
This function enables or disables the update of timeStamps on this oaTech database. TimeStamps are enabled by default.
|
|
||||||||||||
|
This function enables or disables undo for this in-memory image of the technology database. If enabled, all changes made to this tech are logged so that undo() can restore the tech to earlier states. If disabled, undo records are not created, and changes are not logged. This function requires the caller to specify a particular model for undo (oaUndoModelEnum value). When enabling undo, the undoModel argument is required. If disabling undo, the undoModel argument is omitted. When undo is disabled, the current undo log and undo records are discarded. OpenAccess supports two undo models:
If postCheckpoint is specified, a call to undo must immediately follow a checkpoint or an exception is thrown. See Undo and Redo Use Models in OpenAccess for more information.
|
|
||||||||||||
|
This function returns a boolean that indicates whether the specified oaSaveRecover file exists for the tech in the specified library.
|
|
||||||||||||
|
This function returns a boolean that indicates whether the specified oaSaveRecover file exists for the tech in the specified library.
|
|
||||||||||||
|
This function returns true if the tech database is open for the specified library or if a non-zero size tech database for the specified library exists on disk. It returns false otherwise. If the tech is not currently open and if inherited is true (default), this function uses the library's "techLibName" string property to resolve the target library (see the oaTech class description for further information). If inherited is false, the property is ignored and the lookup is done using the specified library only. An oacCannotFindInheritedTechLib exception is thrown if inherited is true and a "techLibName" string property in the target library resolution chain specifies the name of a non-existent library.
|
|
||||||||||||
|
This function returns true if the tech database is open for the specified library or if a non-zero size tech database for the specified library exists on disk. It returns false otherwise. If the tech is not currently open and if inherited is true (default), this function uses the library's "techLibName" string property to resolve the target library (see the oaTech class description for further information). If inherited is false, the property is ignored and the lookup is done using the specified library only. An oacCannotFindInheritedTechLib exception is thrown if inherited is true and a "techLibName" string property in the target library resolution chain specifies the name of a non-existent library.
|
|
|
This function attempts to find an open tech database for the specified library. If the library contains a tech database, and that database is not open, the function returns NULL. If there is no local tech database, and the library uses an attached tech database specified with the "techLibName" property instead, this function recursively attempts to resolve the target library and find the open tech database for the resolved target library. (see the oaTech class description for further information). If successful, the function returns a pointer to the tech database. Otherwise, NULL is returned. An oacCannotFindInheritedTechLib exception is thrown if a "techLibName" string property in the target library resolution chain specifies the name of a non-existent library.
|
|
|
This function attempts to find an open tech database for the specified library name. If the library contains a tech database, and that database is not open, the function will return NULL. If there is no local tech database, if the library uses an attached tech database specified with the "techLibName" property, this function will recursively attempt to resolve the target library and find the open tech database for the resolved target library (see the oaTech class description for further information). If successful, the function returns a pointer to the tech database. Otherwise, NULL is returned. An oacCannotFindInheritedTechLib exception is thrown if a "techLibName" string property in the target library resolution chain specifies the name of a non-existent library.
|
|
|
This function returns a collection of analysis libraries.
|
|
|
This function returns a collection of analysis libraries contained in the graph of tech databases rooted at this oaTech. To return a collection of analysis libraries in the current tech only, refer to the getAnalysisLibs function that takes the filterFlags argument. |
|
|
This function returns a collection of appDefs of the specified data type used in this tech database.
|
|
|
This function returns a collection of appObjectDefs used in this tech database. |
|
|
This function returns a collection of any oaAppObject with the specified extension that exists in this tech database.
|
|
||||||||||||
|
This function gets the name of the library that the specified library lib has a technology attachment to and returns it in attachLibName. It is an error if lib does not have a technology attachment to another library.
|
|
|
This function returns the clearance measure enum value in use. The local argument specifies whether, if true, to look only in this technology database or, if false, to search this technology database and all of its referenced technology databases for the effective clearance measure.
|
|
|
This function returns the clearance measurement enum value used for this technology database and all of its referenced technology databases. |
|
|
This function returns a collection of constraint group headers used by this tech database. Note that the collection can include oaConstraintGroupHeaders with the same name (for default or foundry constraint groups).
|
|
||||||||||||
|
This function returns a collection of constraint groups that are associated with the specified constraintGroupDef.
|
|
|
This function returns a collection of constraint groups.
|
|
|
This function returns a collection of constraint groups in this and all referenced tech databases. To return a collection of constraint groups in the current tech only, refer to the getConstraintGroups function that takes the filterFlags argument. Refer to Incremental Technology Databases in the Using Technology Databases section of the Programmers Guide for more information about referenced tech databases. |
|
|
This function returns a collection of constraint parameters.
|
|
|
This function returns a collection of constraint parameters in this and all referenced tech databases. To return a collection of constraint parameters in the current tech only, refer to the getConstraintParams function that takes the filterFlags argument. |
|
||||||||||||
|
This function returns a collection of constraints that match the given constraint definition.
|
|
|
This function returns a collection of constraints with the specified definition in this and any referenced tech databases. If no definition is specified, all the constraints are returned. To return a collection of constraints in the current tech only, refer to the getConstraints function that takes the filterFlags argument.
|
|
|
This function returns the ID of the last checkpoint set in this tech. If the ID is not set on that checkpoint, this function returns UINT_MAX. |
|
|
This function returns the time at which this tech database was created. |
|
||||||||||||
|
This function returns the database-units per user-unit for the specified view type. The local argument specifies whether, if true, to look only in this technology database or, if false, to search this technology database and all its referenced technology databases for the effective database-units per user-unit.
|
|
|
This function returns the database-units per user-unit for the specified viewType used for this technology database and all of its referenced technology databases. Both this value and the user-units type must be used to calculate the real distance meant by lengths and coordinates stored in an OpenAccess database.
The viewTypes allowed in this call are the subset of oaReservedViewType values that are used as viewTypes for an oaDesign. These are:
The caller can construct the viewType inline with this function call as in:
|
|
|
This function returns the default clearance measure enum value. |
|
|
This function returns the default constraint group for this technology. If no constraints have been set on the default constraint group, a new constraint group is created and returned. |
|
|
This function returns the default database-units per user-unit for the specified viewType. These are the static values that will be returned by getDBUPerUU() when no call to setDBUPerUU has been made for a given viewType.
The viewTypes allowed in this call are the subset of oaReservedViewType values that are used as viewTypes for an oaDesign. These are:
The caller can construct the viewType inline with this function call as in:
|
|
|
This function returns the default value for the default manufacturing grid.
|
|
|
This function returns the default boolean value indicating whether or not the gates are considered grounded. |
|
|
This function returns the manufacturing grid that applies to all physical layers unless it has been overridden at the physical layer level. The local argument specifies whether, if true, to look only in this technology database or, if false, to search this technology database and all of its referenced technology databases for the effective manufacturing grid.
|
|
|
This function returns the manufacturing grid that applies to all physical layers unless it has been overridden at the physical layer level. |
|
|
This function returns the requested user-unit information from the tech database for the specified viewType.
Note: Although users can construct their own oaViewTypes, valid viewTypes for this function are restricted to the set of reserved viewTypes, namely, an oaReservedViewType object constructed with one of the following reserved view type enumerated constants:
The developer can call oaViewType::get(oaReservedViewType) to construct and return a pointer to an a oaViewType object using one of the valid reserved viewType enumerated constants (for example,
|
|
|
This function returns a collection of derivedLayer parameters.
|
|
||||||||||||
|
This function returns the data model revision number for the database, as well as an array of the features currently in the database. The application can iterate through the array to get the ID for each feature present. Each feature ID corresponds to an oaFeatureIDEnum value.
|
|
|
This function returns the constraint group that represents the foundry rules for this technology. |
|
|
This function returns a collection of groups in this tech database with the specified group definition.
|
|
|
This function returns the complete set of groups in this tech database. |
|
|
This function returns a collection of group names for the specified extension in this tech database.
|
|
|
This function returns the time at which this tech database was last modified. |
|
|
This function returns a collection of layerHeaders in this tech database. |
|
|
This function returns a collection of layers. The filterFlags value defines the extent of the collection.
|
|
|
This function returns a collection of layers this and all referenced tech databases. To return a collection of layers in the current tech only, refer to the getLayers function that takes the filterFlags argument. |
|
|
This function returns a pointer to the library object containing this tech database. |
|
||||||||||||
|
This function returns the name of the library associated with this tech database.
|
|
|
This function returns the name of the library associated with this tech database.
|
|
|
This function returns the mode of the currently open tech database. |
|
|
This function returns the number of undo records on the most recent checkpoint saved for this tech. |
|
|
This function returns the number of undo records that will be removed if an undo command is issued. The value returned depends on the undo model in use. If the undo model is oacUndoModelPostCheckpoint, the function returns the number of undo records before the last checkpoint. If the undo model is oacUndoModelPreCheckpoint, the function returns the number of undo records after the last checkpoint. For more information about undo models, refer to Undo and Redo Use Models in OpenAccess in the Programmers Guide. |
|
|
This function returns a collection of currently open tech databases. |
|
|
This function returns a collection of operating points. The filterFlags value defines the extent of the collection.
|
|
|
This function returns a collection of operating points in this and all referenced tech databases. To return a collection of operating points in the current tech only, refer to the getOpPoints function that takes the filterFlags argument. |
|
||||||||||||
|
This function retrieves the processFamily attribute and returns it in the processFamily string. If the processFamily attribute is unset, the empty string is returned.
|
|
|
This function returns a collection of purposes.
|
|
|
This function returns a collection of purposes in this and all referenced tech databases. To return a collection of purposes in the current tech only, refer to the getPurposes function that takes the filterFlags argument. |
|
|
This function returns the time this tech database was read. |
|
|
This function returns the number of times this tech database was opened without closing. This number includes both internal and external openings. |
|
|
This function returns the revision number for the tech database. |
|
|
This function returns a collection of siteDefs.
|
|
|
This function returns a collection of siteDefs in this and all referenced tech databases. To return a collection of siteDefs in the current tech only, refer to the getSiteDefs function that takes the filterFlags argument. |
|
||||||||||||
|
This function returns an ordered list of tech database headers that are referenced by this tech database. If there are no references, an empty array is returned. Refer to Incremental Technology Databases in the Using Technology Databases section of the Programmers Guide for more information about referenced tech databases.
|
|
|
This function returns the timeStamp value for the specified application object.
|
|
|
This function returns the timeStamp value for the specified technology datatype.
|
|
|
This function returns the undo model specified when calling enableUndo(). If this function is called and undo is not enabled, the default value of oacUndoModelNotSpecified is returned. |
|
|
This function returns a collection of techHeaders in other open tech databases that contain references to this tech database. |
|
||||||||||||
|
This function returns the user-unit information for the specified viewType. The local argument specifies whether, if true, to look only in this technology database or, if false, to search this technology database and all of its referenced technology databases for the effective user-unit.
|
|
|
This function returns the user-unit information for the specified viewType used for this technology database and all of its referenced technology databases.
Note: Although users can construct their own oaViewTypes, valid viewTypes for this function are restricted to the set of reserved viewTypes, namely, an oaReservedViewType object constructed with one of the following reserved view type enumerated constants:
The developer can call oaViewType::get(oaReservedViewType) to construct and return a pointer to an a oaViewType object using one of the valid reserved viewType enumerated constants (for example,
|
|
|
This function returns a collection of values.
|
|
|
This function returns a collection of values in this and all referenced tech databases. To return a collection of values in the current tech only, refer to the getValues function that takes the filterFlags argument. |
|
|
This function returns a collection of viaDefHeaders in this tech database. |
|
|
This function returns a collection of viaDefs.
|
|
|
This function returns a collection of viaDefs in this and all referenced tech databases. To return a collection of viaDefs in the current tech only, refer to the getViaDefs function that takes the filterFlags argument. |
|
|
This function returns a collection of viaSpecs.
|
|
|
This function returns a collection of via specs in this and all referenced tech databases. To return a collection of via specs in the current tech only, refer to the getViaSpecs function that takes the filterFlags argument. |
|
|
This function returns a collection of viaVariantHeaders.
|
|
|
This function returns a collection of oaViaVariants.
|
|
|
This function returns true if the technology library lib has a technology attachment to another library.
|
|
|
This function returns a boolean indicating whether or not there is a default constraint group for this tech database. |
|
|
This function checks this database for a processFamily attribute if local is true, or if local is false, checks all databases in the graph of techs for a processFamily attribute. The function returns true if the processFamily attribute is set and returns false if the attribute is not set.
|
|
|
This function returns true if this database has unbound tech database references (or if it has no tech database references). Otherwise, false is returned. The existence of an unbound tech database reference affects the search order when looking up technology objects in incremental tech databases. For more information about the search order, refer to Referencing Technology Databases in the Programmers Guide. |
|
|
This function returns true if the clearance measure attribute is explicitly set in the technology database; false is returned otherwise. |
|
|
This function returns true if the DBUPerUU attribute for the specified viewType is explicitly set in the technology database; false is returned otherwise.
|
|
|
This function returns true if the default manufacturing grid attribute is explicitly set in the technology database; false is returned otherwise. |
|
|
This function returns a boolean indicating whether or not the gates are considered grounded. The local argument specifies whether, if true, to look only in this technology database or, if false, to search this technology database and all of its referenced technology databases for the effective boolean value.
|
|
|
This function returns a boolean value indicating whether or not the gates are considered grounded in this tech database. |
|
|
This function returns true if the gates-are-considered-grounded attribute is explicitly set in the technology database; false is returned otherwise. |
|
|
This function determines whether this technology database in memory is currently in an undo or redo operation.
|
|
|
This function returns a boolean value that indicates if this tech database has been modified but not saved. |
|
|
This function returns a boolean that indicates whether this tech was recovered from a critical save or an auto save database file. For information about how to use a recover type database to restore a design, see the Programmers Guide article OpenAccess Libraries and Design Management. |
|
|
This function determines whether undo is enabled for this technology database in memory.
|
|
|
This function returns true if the user-unit attribute for the specified viewType is explicitly set in the technology database; false is returned otherwise.
|
|
|
This function minimizes the amount of virtual memory this tech is currently using. It releases dynamically allocated data structures that can be rebuilt as needed. Applications can call this function after creating a tech or making significant edits to an existing tech, before starting a phase of processing that interacts with the tech in different ways. This function should be called sparingly, as it can have a substantial impact on the performance of subsequent operations. |
|
||||||||||||
|
This function opens the tech database for the specified library with the specified access mode. Note that the open functions do not create tech databases, they simply open them. The tech to be opened might reference other techs in a graph. If so, OpenAccess attempts to open the referenced techs as well. If one of the referenced techs was edited out of context, conflicting technology objects might be encountered. It is an error if opening a tech:
OpenAccess issues onConflict observer notifications and issues exceptions for conflicting objects in different techs in the graph. It also issues onProcessFamilyConflict and onExcludedLayerConflict for processFamily attribute conflicts or excluded layer conflicts. For more information about referenced tech databases, refer to Incremental Technology Databases in the Using Technology Databases section of the Programmers Guide.
|
|
||||||||||||
|
This function opens the tech database for the specified library with the specified access mode. Note that the open functions do not create tech databases, they simply open them. The tech to be opened might reference other techs in a graph. If so, OpenAccess attempts to open the referenced techs as well. Refer to Incremental Technology Databases in the Using Technology Databases section of the Programmers Guide for more information. If one of the referenced techs was edited out of context, conflicting technology objects might be encountered when opening the tech. It is an error if opening a tech:
OpenAccess issues observer notifications and exceptions for conflicting objects in different techs in the graph. It also issues onProcessFamilyConflict and onExcludedLayerConflict for processFamily attribute conflicts or excluded layer conflicts. Refer to Conflicts in Incremental Technology Databases in the Using Technology Databases section of the Programmers Guide for more information.
|
|
|
This function closes this tech database, removing it from memory regardless of its reference count. |
|
||||||||||||
|
This function attempts to recover the tech with the specified saveRecover type in the specified library. If successful, the tech is returned.
|
|
|
This function restores the state of the in-memory image of the technology database to its state before the last undo. The records are stored using either a pre-checkpoint or post-checkpoint model. This call reverses the changes only if undo is enabled, undo() was called for this tech, and no changes occurred since the last undo(). The redo operation starts from the most recent record and restores the one transaction defined by both the checkpoint and the undo model. Refer to the Undo and Redo Use Models article for additional information. If there is an enabled observer on the action that is completed as a result of the redo operation, that observer is called. In addition, there are observers for the redo operation itself. Refer to oaTechUndoObserver for more information.
|
|
|
This function reopens this tech database using the specified access mode. You can reset or truncate the contents of the tech database depending on the new access mode. This function does not affect the reference count of the tech database.
|
|
|
This function reloads the contents of this tech database from disk. If the tech database is open in write mode, it is simply truncated. This function does not affect the access mode of the tech database. |
|
|
This function saves the oaSaveRecoverType file to disk.
|
|
|
This function saves the tech database to disk. The tech remains open and all of its in-memory data remains valid.
|
|
|
This function saves the tech database to the disk in the tech file associated with the specified library name. The tech remains open and all of its in-memory data remains valid.
|
|
|
This function sets the clearance measurement value for this technology database.
|
|
|
This function sets an undo checkpoint for the in-memory image of this technology database. A checkpoint marks a state of the tech. If undo is enabled, each call to undo() restores the tech to the state marked by the previous checkpoint. The checkpoint has a user-specified ID, which can be used to assist in keeping track of checkpoints. If not specified, a unique value of checkPointID is automatically assigned to the checkpoint by OpenAccess.
|
|
||||||||||||
|
This function sets the database-units per user-unit information in the technology database for the specified viewType.
The viewTypes allowed in this call are the subset of oaReservedViewType values that are used as viewTypes for an oaDesign. These are:
The caller can construct the viewType inline with this function call as in: Note: Significant flow issues result when you combine layouts that use different DBUPerUU settings in a project resulting in a single mask. To avoid any issues, use a single DBUPerUU setting that is a function of the manufacturing grid for the given technology, as outlined in the following table.
|
|
|
This function sets the manufacturing grid that applies to all physical layers unless it has been overridden at the physical layer level.
|
|
|
This function sets the gateGrounded attribute in this technology database.
|
|
|
This function sets the processFamily attribute for this technology database. When called, this function replaces the current processFamily attribute unless doing so causes an error. It is an error if a tech, in any technology database graph that this tech is part of, has a different processFamily attribute already set. Setting the processFamily to its current value does not produce an error. If you call this function with an empty string, the processFamily attribute is unset.
|
|
|
This function sets the tech database references for this tech. A reference is a mechanism that allows this tech database to inherit information from other techs. The set of referenced tech databases is known as the graph of techs. This function removes any previously existing references (as a result, some oaTechLayerHeaders and oaTechViaDefHeaders may become and remain unbound). An oacTechSetRefsConflicts exception is thrown if this function:
An oacTechCannotSetDuplicateRefs exception is thrown if this function attempts to set duplicate tech database references on a tech database. An oacTechSetRefsCircularReference exception is thrown if an attempt is made to set a reference on this database so that its graph chain refers back to this tech db (if techA->techB->techC and this function attempts to set techC->techA). OpenAccess issues onConflict observer notifications and issues exceptions for the above errors. OpenAccess also issues onProcessFamilyConflict and onExcludedLayerConflict observer notifications for processFamily attribute conflicts or excluded layer conflicts. When setRefs() is used, pre and post-modify observers are called from oaObserver<oaTech> using the oacSetRefsTechModType. For more information about setting references, refer to Incremental Technology Databases in the Using Technology Databases section of the Programmers Guide.
|
|
||||||||||||
|
This function sets the user-unit information in the technology database for the specified viewType.
Note: Although users can construct their own oaViewTypes, valid viewTypes for this function are restricted to the set of reserved viewTypes, namely, an oaReservedViewType object constructed with one of the following reserved view type enumerated constants:
The developer can call oaViewType::get(oaReservedViewType) to construct and return a pointer to an a oaViewType object using one of the valid reserved viewType enumerated constants (for example,
|
|
|
This function reverts the changes made to the in-memory image of this technology database. Undo records are stored using either a pre-checkpoint or post-checkpoint model. This function steps back one checkpoint to the most recent checkpoint and reverses the changes saved in the undo records. The undo operation starts from the most recent record and reverses the one transaction defined by both the checkpoint and the undo model. Refer to the Undo and Redo Use Models article for additional information. If there is an enabled observer on the action that is completed as a result of the undo operation, that observer is called. In addition, there are observers for the undo operation itself. Refer to oaTechUndoObserver for more information. Note that only changes to managed objects in the oaTech are reversed. Utility objects that contain pointers to a managed object are not affected.
|
|
|
This function reverts the clearance measure attribute back to its unset state in the technology database.
|
|
|
This function removes the last checkpoint in this tech assuming that there are no undo records after the last checkpoint. Otherwise, an exception is thrown. See oaTech::getNumUndoCpRecs() for getting the number of undo records after the checkpoint.
|
|
|
This function reverts the database-units per user-unit attribute for the specified viewType back to its unset state in the technology database.
|
|
|
This function reverts the default manufacturing grid attribute back to its unset state in the technology database.
|
|
|
This function reverts the gates-are-considered-grounded attribute back to its unset state in the technology database.
|
|
|
This function unsets the processFamily attribute to the empty string for this technology database. |
|
|
This function removes all references to other tech databases. No operation is performed if this tech database has no references. For more information about tech database references, refer to Incremental Technology Databases in the Using Technology Databases section of the Programmers Guide. Removing existing oaTech database references might cause some oaTechLayerHeaders and oaTechViaDefHeaders to become unbound and remain that way.
|
|
|
This function reverts the user-unit attribute for the specified viewType back to its unset state in the technology database.
|
|
||||||||||||
|
This function converts the user units into database units for the specified viewType.
The viewTypes allowed in this call are the subset of oaReservedViewType values that are used as viewTypes for an oaDesign. These are:
The caller can construct the viewType inline with this function call as in:
|
|
||||||||||||
|
This function converts the area in square user units to an area in square database units for the specified viewType.
The viewTypes allowed in this call are the subset of oaReservedViewType values that are used as viewTypes for an oaDesign. These are:
The caller can construct the viewType inline with this function call as in:
|
|
||||||||||||
|
This function converts the user-unit distance to database-unit distance for the specified viewType.
The viewTypes allowed in this call are the subset of oaReservedViewType values that are used as viewTypes for an oaDesign. These are:
The caller can construct the viewType inline with this function call as in:
|
|
|
This function returns false if there are multiple objects with the same attributes or conflicting parameter values in the technology database graph rooted at this tech database. It returns true otherwise. OpenAccess issues onConflict observer notifications for conflicting objects in different techs in the graph. It also issues onProcessFamilyConflict and onExcludedLayerConflict for processFamily attribute conflicts or excluded layer conflicts. For more information, refer to Incremental Technology Databases in the Using Technology Databases section of the Programmers Guide. |
|
|
|
Copyright © 2002 - 2010 Cadence Design Systems, Inc.
All Rights Reserved.