UndoQueue.UndoQueue Class Reference
#include
<class_undo_queue_1_1_undo_queue.h>
Inheritance diagram for
UndoQueue.UndoQueue:
Public Member Functions |
|
| __init__ () | |
| registerQueueChangedCallback () | |
| flush () | |
| add () | |
| Same as MessageQueue.add() except that it
also checks OPEN_CHUNK and CLOSE_CHUNK messages. |
|
| addMessage () | |
| If you have created a message using the
createMessage()
method, you should use this one instead of just add. |
|
| addList () | |
| Adds a list of well-formed messages to the
queue. |
|
| dequeue () | |
| reset () | |
| Clear the undo queue and the local open
chunk list. |
|
Member Function Documentation
| UndoQueue.UndoQueue.__init__ | ( | ) |
Reimplemented from MessageQueue.MessageQueue.
| UndoQueue.UndoQueue.registerQueueChangedCallback | ( | ) |
| UndoQueue.UndoQueue.flush | ( | ) |
| UndoQueue.UndoQueue.add | ( | ) |
Same as MessageQueue.add() except that it also checks OPEN_CHUNK and CLOSE_CHUNK messages.
Issues warnings for these cases:
- OPEN_CHUNK of a previous chunk that was never closed
- CLOSE_CHUNK without a prior OPEN_CHUNK
- CLOSE_CHUNK immediately after a OPEN_CHUNK, ie. an empty chunk
Reimplemented from MessageQueue.MessageQueue.
| UndoQueue.UndoQueue.addMessage | ( | ) |
If you have created a message using the createMessage() method, you should use this one instead of just add.
Reimplemented from MessageQueue.MessageQueue.
| UndoQueue.UndoQueue.addList | ( | ) |
Adds a list of well-formed messages to the queue.
All messages will be added as one 'chunk', the queue is locked before the first message is added and unlocked after the last message.
Reimplemented from MessageQueue.MessageQueue.
| UndoQueue.UndoQueue.dequeue | ( | ) |
| UndoQueue.UndoQueue.reset | ( | ) |
Clear the undo queue and the local open chunk list.
