[question] do you have any example?

[moebiussurfing]

hey, do you have some progress on this?
cheers

[sphaero]

I do, but it's now based on Dear Imgui see: https://github.com/rokups/ImNodes

[moebiussurfing]

cool. I see your both forks here for ImNodes and ofxImGui (1.72)
any chance that your share some screenshot?
just curious, but are you linking between source/target ofParameters maybe?

[moebiussurfing]

I have seen another repo similar to ImNodes:
https://github.com/thedmd/imgui-node-editor

btw there's several forks to ofxImGui...
https://github.com/JoshuaBatty/ofxNodeGraph

Should be nice to have more ported to OF with docking, tabs, nod graph etc

[sphaero]

I'm familiar with all those options. The reason I chose ofxImGui is because it lets me use ImGui natively which allows to move out of openframeworks optionally. So ofxImGui lets you use any branch of ImGui including docks and tabs. My fork of ofxImGui does nothing special other than upgrading the ImGui version included. See jvcleave/ofxImGui#96 for example. I don't why it doesn't get merged but a +1 would help?

[moebiussurfing]

thanks for your explanations. I did a +1 to it.

Same happens (not merging by owner) in another fork that adds multi window:
jvcleave/ofxImGui#91
it has some bug when closing, but the thing is that it handles multiple contexts, so I can use several ofxImGui instances around many classes, not just one only like on the master branch.

[moebiussurfing]

hey @sphaero , sorry to ask here again...

I tested your recommendation of https://github.com/rokups/ImNodes but I can't compile the snipped example. It's crashing on runtime on starting.
(Not sure if it could be bc ImGui is newer than the 1.72)

I am looking to a very simple OF patch system, to route from:
a node with 8 out to ->
another node with 8 in, just this.

Instead of this, I am trying to get this repository running and I think I am near...
So maybe you can help me with some tips...

I added the nodes types I need and worked fine, but I don't know how to get the patching states after user patching.

//NodesEdit.h
//DEFINE NODE TYPES
////////////////////////////////////////////////////////////////////////////////
static const std::vector<ImGui::NodeType> node_types =
{
    {
        { std::string("OUTPUT") },
        {
            { std::string("channel1"), std::string("er"), std::string("f") },
            { std::string("channel2"), std::string("er"), std::string("f") },
            { std::string("channel3"), std::string("er"), std::string("f") },
            { std::string("channel4"), std::string("er"), std::string("f") },
        }
    },
    {
        { std::string("INPUT") },
        {
            { std::string("channel1"), std::string("ew"), std::string("f") },
            { std::string("channel2"), std::string("ew"), std::string("f") },
            { std::string("channel3"), std::string("ew"), std::string("f") },
            { std::string("channel4"), std::string("ew"), std::string("f") },
        }
    }
};  

I can see on the log witch nodes have been connected by the user, but not which inputs/output pins are linked:

For the moment I don't need more features like other ImGui nodes libs... So would be nice to use yours, In case this is implemented.
(The only other thing could be cool is to set the patch wires by code to load settings from xml/json too.)

Thanks for this repo and your attention,
Regards

[sphaero]

I'm not sure I understand the question. However I really recommend using ImNodes. It's much more immediate mode. I've completely switched to it

[moebiussurfing]

ok. Thanks. I'll try again to solve the exceptions I am getting with ImNodes.
If you have some OF code /snippet using ImNodes to share will be appreciated.

I'm not sure I understand the question.

What I mean on the above question is to know:
how to get what connections between nodes are done by the user.
Looking on the screenshot for the 1st link wire. This is what I want to get:

Wired Link #1 info:
Node "OUTPUT1" from pin "channel 2" 
    is connected to ->
Node "INPUT2" on pin "channel 4"

Wired Link #2 info:
...