Is it bad idea have one timer just calling a bunch of functions that draw and handle mouse events or drag and drop zones within juce itself rather everything in classes . Free animation as well described in this talk
Of course you would have to rewrite a lot of this logic without look and feel and parameter attachment perks but only has to be done once .
Knob(“param1”,graphicVar,Mouse, bounds);
Knob(“param2”, graphicVar,Mouse,bounds) ;
ComboBox(“param3”,bounds);
1 Like
JUCE is already immediate mode - i.e. when you write graphics code the changes are applied immediately rather than going into a rendering queue and applied asynchronously.
The main difference between JUCE’s API and ImGui is that JUCE is object-oriented whereas ImGui is procedural. You could absoluately write a procedural wrapper around JUCE’s API.
JUCE is already immediate mode
Your comment relates to the Graphics API and OP is talking about something else. As mentioned in the talk at 07:40 the term derives from the same meaning you referred to so that certainly contributes to the confusion.
1 Like
I was just pointing out that from OP’s example code it looks like they’re asking about whether a procedural GUI API would work for JUCE, not whether immediate mode would work since that’s already how JUCE works.
procedural would have been a better word to use. It looks super clean to me for smaller projects.
1 Like