Nodes (objects) port from ofxDatGui --> ImGui about mosaic

[d3cod3]

[d3cod3]

I'm having trouble drawing OF stuff inside objects, it seems like imgui is always rendering on top of everything.

In the image you can see the video grabber object rendering the webcam image under the object window.

Did you know how to solve this?

[Daandelange]

Hmm, I didn't think about that case where you need to draw the GUI from OF.
One way would be to let objects draw after ImGui has flushed the graphics pipeline, so you can draw on top of it. (This happens when you call ofxImGui->end() in auto mode or ofxImGui->draw() in manual mode with my fork.)
Otherwise, we might be able to make a transparent zone so we can draw behind objects.
Both feel pretty hacky...

Another option is to link a texture-ID in order to display images. An image tex id can be an FBO tex ID, I think.
Do lots of objects have/need "custom GUIs" ? (involving drawing from OF)

[d3cod3]

Basically most of the objects that works with video/webcam/images, drawing ofTextures inside the objects, and sound objects with signal waveform visualizer (ofPolyline) or fft data (audio analysis).

The linking of a texture id from an FBO seems the better choice, i'll check it.

Don't like the transparent zone option, but i'm going to try them all and we'll talk again.

[d3cod3]

Got it!

using ofTexture with proper allocate:

ofTextureData texData;
texData.width = camWidth;
texData.height = camHeight;
texData.textureTarget = GL_TEXTURE_2D;
texData.bFlipTexture = true;
static_cast<ofTexture *>(_outletParams[0])->allocate(texData);

and calling a method from ofxImGui helpers did the trick:

ofxImGui::AddImage(*static_cast<ofTexture *>(_outletParams[0]), ImVec2(this->width*_nodeCanvas.GetCanvasScale(), this->height*_nodeCanvas.GetCanvasScale()));

So, problem solved, for ofPolyline waveform graphics, with ofTexture.bind()/unbind() will work!

[Daandelange]

Yes, the FBO option would be the best option, that keeps Gui separated and "canalised" (with API methods). (don't spend too much time on the other solutions?)
Seems pretty simple to do in fact.
One drawback with FBOs : on small hardware (with integrated GPU), we'll have to check what the FBO limit is and what happens when there's too much FBO objects to allocate ? We can always disable preview mode on nodes if hardware doesn't allow having too much.

For plotting, checkout the ImGui demo ImGui::PlotHistogram(), eventually some ImGuiExtension. Although drawing the GUI with OF will give a better example on how to use object data ?

Edit: Ok, great, works fine for FBOs. :)

[d3cod3]

Actually there's no need for FBO, just using the link ofTexture pointer, so no GPU limits problem, it works like a charm!

But is a really good idea to have a mechanism enabling/disabling automatic preview depending on the resources

Great the plotting from imgui, i'll check it!

[d3cod3]

Porting objects...

[d3cod3]

oscillator and envelopes sound objects

this starts to look good!