Skip to content

Customizing action behavior and appearance

Thomas Kroes edited this page Dec 17, 2025 · 1 revision

ManiVault’s actions offer numerous customization options, enabling both plugin developers and application designers to tailor the behavior and appearance of these GUI blocks.

Customization by Plugin Developers (Design-Time)

When coding a plugin, developers can configure each action’s properties and options to suit the plugin’s needs. Some examples:

  • Default Values & Ranges
    When instantiating an action, you can provide default values. For numeric actions, you can also set ranges (min/max) and step sizes. This defines the allowed input domain and initial state of the control.

  • Widget Configuration
    Many actions support flags or parameters to adjust their visual component. For instance, a DecimalAction can be configured to show a slider, a spinbox, or both. If a parameter makes sense as a slider (e.g. 0 to 100), the developer can enable the slider control; if fine-grained numeric input is needed, they might show just a spinbox. In fact, ManiVault’s decimal action lets you specify which sub-widgets to include, and will create them on-the-fly and keep them in sync (typing in the box moves the slider, and vice-versa). Similarly, StringAction can be either a single-line text field or a multi-line text area depending on a flag – you might choose a multi-line TextEdit for long text input versus a LineEdit for short text. Read this tutorial on how to set widget flags.et widget flags.

Clone this wiki locally