|
Class |
Description |
|---|
 AcTransaction |
Transactions provide a way to extend the boundary of operation on an object beyond open and close, and avoid those vexing open conflict errors. They also improve performance by being lenient on multiple open requests while postponing all the opened objects close-time work to the end of the transaction.The transaction mechanism runs in parallel with the acdbOpenObject() and close() mechanism. This means that both can be in effect at the same time with AcDb::kForWrite status in both. For more information on this, see the section on transactions in the ObjectARX Developer's Guide. |
| AcTransactionManager |
There is a single object of class AcTransactionManager created by the ObjectARX system when AutoCAD first starts up. This AcTransactionManager object is globally available to all ObjectARX applications. The macro actrTransactionManager returns a pointer to the system AcTransactionManager object to allow access to its member functions.The system AcTransactionManager object is used to start, end, or terminate transactions. In addition, it provides functionality to manage transactions and the objects within them.For more information on the transaction mechanism, see the transaction section in the ObjectARX Developer's Guide. |
| AcTransactionReactor |
The AcTransactionReactor class is designed to be used as a base class for custom reactor classes defined in ObjectARX applications. Such custom classes would override the desired member functions of the base class to receive notification of desired events occurring within the transaction manager for ObjectARX. See the notification section of the ObjectARX Developer's Guide for more information on the reactor mechanism.While it is possible to instantiate objects of the AcTransactionReactor class, the member functions of the AcTransactionReactor class have empty default implementations (that is, they simply return when called), so objects of this class do nothing but waste... more |
