imgui_juce

JUCE backend for Dear ImGui.

I don't recommend using JUCE for prototyping DSP code, but if you have no better options, using ImGui with this library should make your life a lot easier.

Pros:

• No more listener/attachment/callback bullshit (you won't believe how many layers of callbacks are used just to set a single parameter using APVTS's SliderAttachment).

  You can write declarative code for GUI now:

  ImGui::Text("Hello, world %d", 123); if (ImGui::Button("Save")) DoStuff();

• No more GUI layout positioning bullshit. Spend your time on DSP code.

• It's much easier now to integrate custom non-float parameters into your plugin.

• There are a ton of useful extensions for ImGui you can use for easier debugging. See imnodes, implot, and the list on ImGui wiki.

• You can mix JUCE GUI components and ImGui. ImGui only needs a Component for mouse/keyboard input and a OpenGLContext for rendering. You can, for example, only enable the ImGui component for debugging and disable it in the final release.

Cons:

• GUI is recomputed each frame at 60 FPS, probably less efficient than JUCE, but at least it's using OpenGL.

• JUCE's keypress callbacks are extremely inefficient for ImGui, though you can disable it by setting

  setWantsKeyboardFocus(false);

• Component and layout can be less customizable than JUCE. You probably only want to use it for prototyping.

• Slider skew not supported by default. You need to write your own component for that (contributions welcome). ImGui do have logarithmic slider built-in though.

• You need a patched version of ImGui for use in audio plugins (see Note below).

Usage

The backend exposes three functions

You need to create a juce::OpenGLRenderer and call the three functions in

respectively. See

for a complete minimal working example.

If you need an audio plugin example, see

CMake Usage

If you are using CMake, call add_subdirectory on the current directory after JUCE directory is added. Then link your application target to imgui_imple_juce. For example,

See

for a complete example.

Note

By default ImGui only support a single instance running because it uses a global state

This is probably fine if you are writing a GUI application, but if you are writing an audio plugin, the plugin will crash if you add multiple instances of the plugin in DAW and open two GUIs at the same time.

You need to patch ImGui and make the global state thread local

in order to support multiple instances of ImGui running at the same time on different threads. See

for details.

You need a similar patch if you want to use imnodes or ImPlot in your plugin. For a ImPlot example, see

License

The imgui_juce library is licensed under the GNU Lesser General Public License v3.0 (LGPLv3).

Examples are placed under public domain.

Donate

If this library saves valuable development time for you, consider donate to support this project:

---