-
-
Notifications
You must be signed in to change notification settings - Fork 7
Undo Redo module
The undo/redo module provides support for undo/redo operations.
To enable the plotting module, update your uvproj.yaml so that the undo_redo key under enabled-modules is set to true like this:
name: "MyProject"
version: "1.0.0.0"
engine-version: "1.0.0.0"
enabled-modules:
undo_redo: trueThen, regenerate the modules cache by running the following command:
user $ ./UVKBuildTool --generate <project directory>
After that, refresh your CMake project with cmake ..!
Next, in your source file, include the Modules.hpp header in your components like this:
#include <Modules/Modules.hpp>The entire module is flagged as event safe at Post-begin.
The module stores data in the Transaction data type, as can be seen below:
struct UIMGUI_PUBLIC_API Transaction
{
std::function<void(TransactionPayload&)> undofunc;
std::function<void(TransactionPayload&)> redofunc;
TransactionPayload payload;
};The 2 functions are the events to be called on undo and redo, respectively.
The payload member is of type TransactionPayload which is a simple struct storing a void* for a buffer and
its size like this:
struct UIMGUI_PUBLIC_API TransactionPayload
{
void* payload;
size_t size;
};So to push a transaction create a transaction, initialise the events and the payload and push it as an argument to
the push function like this:
Transaction transaction =
{
.undofunc = [](TransactionPayload&){ Logger::log("Undo", UVKLog::UVK_LOG_TYPE_NOTE); },
.redofunc = [](TransactionPayload&){ Logger::log("Redo", UVKLog::UVK_LOG_TYPE_NOTE); },
.payload =
{
.payload = nullptr,
.size = 0,
}
};
UImGui::StateTracker::push(transaction);And now you have added an action that can be undone.
By default, push also accepts a bool bRedoIsInit default argument, which is set to false. When set to true it will execute the redo function after the transaction is added to the state tracker. This is made to allow emulating the command pattern more closely.
To undo or redo an action, simply call the undo or redo member functions of the StateTracker class like this:
UImGui::StateTracker::undo();
UImGui::StateTracker::redo();and you should get the appropriate output logged to the console.
To check for the module at compile time, use the UIMGUI_UNDO_MODULE_ENABLED macro.
Runtime checking can be done using the undo_redo member of the ModuleSettings struct. More info can be found
here.
The undo module contains a C API, which uses the standard C API development principles, as defined here. Here is how they differ:
-
TransactionPayloadis renamed toUImGui_TransactionPayload- same content -
push,undoandredofunctions are prefixed withUImGui_StateTracker_ -
pushtakesUImGui_CTransactioninstead ofTransaction -
UImGui_CTransactioninstead ofTransaction. It looks like this:typedef struct UIMGUI_PUBLIC_API UImGui_CTransaction { UImGui_CTransactionCallbackFun undoFunc; UImGui_CTransactionCallbackFun redoFunc; UImGui_TransactionPayload payload; } UImGui_CTransaction;
where UImGui_CTransactionCallbackFun is a C function pointer of type void(UImGui_TransactionPayload*).
This project is supported by all the people who joined our discord server and became beta testers. If you want to join the discord you can click here.
- Home
- Beginner content
- Install guide
- Creating and using the UI components
- The Instance
- The Init Info struct
- Building better titlebar menus
- Textures
- Logging
- Unicode support
- Additional features
- Client-side bar
- Custom type definitions
- Memory management
- C API development
- Config files and Folders
- Interfaces
- Internal Event safety
- Customising the build system
- Modules system
- Collaborating with others
- Advanced content
- Loading dynamic libraries at runtime
- Understanding the library layout
- Compilation mode modifiers
- Supporting plugins
- Production export and deployment
- OS integration tips
- Targeting WASM
- Using a custom rendering engine:
- Using a custom windowing backend:
- Developer and contributor resources
- Misc