Standalone settings-chrome navigation for plugin editors. More...
Go to the source code of this file.
Namespaces | |
| namespace | pulp |
| namespace | pulp::format |
| What the product grants a device: the quota table indexed by capability tier and live thermal state. | |
Functions | |
| view::TabPanel * | pulp::format::enclosing_settings_chrome (view::View *from) |
| The nearest TabPanel ancestor of from, or nullptr. | |
| bool | pulp::format::standalone_settings_available (view::View *from) |
| True when from is hosted in the standalone settings chrome (a TabPanel ancestor carrying the Settings tab alongside the editor). | |
| void | pulp::format::open_standalone_settings (view::View *from) |
| Switch the enclosing standalone chrome to its Settings tab (Audio/MIDI). | |
Standalone settings-chrome navigation for plugin editors.
The standalone host wraps a plugin editor and an Audio/MIDI Settings panel in a tab-bar-less TabPanel (editor = tab 0, "Settings" = tab 1). A plugin editor can add its OWN control — e.g. a gear button — that opens the Settings panel, but ONLY when it is actually hosted in the standalone: inside a DAW the host owns audio + MIDI routing, so there is no settings tab. These helpers give editors a one-call, structure-agnostic way to both detect the chrome and open settings, without reaching into its internals. They are the editor-side mirror of the Settings panel's "Done" button (which switches back to the editor tab).