connorjak / imgui-node-editor Goto Github PK

At the most basic level, this would be determining the overlap in protocols supported on a certain link, and maybe making that visible on the link somehow. For protocol mismatches (no overlap), that could trigger an error?

I could go further and try to do things with more than just the adjacent devices (like skipping through devices without listed protocols (which might just be a cable)).

This would extend the tool to take care of internal components as well as peripherals. We have the technology!

Might be easiest to just serialize absolutely everything; no filepaths or validation needed.

• Every single node gets its name, males, females, and description serialized (nothing in there to prevent repeated data)
• Save node locations
• Save node links (might require serial-ID saving too if I want it to be easy)

There might already be some code for this in the node editor example code?

I could either do this as an extension of Protocol stuff (along with other protocols having more advanced specs, like maybe Thunderbolt 3?) or as a separate mechanism that is checked apart from Protocols.

Not sure how to do this but it would probably be straightforward to accept an estimated bandwidth / power draw on certain parts, and have an overall max bandwidth/power draw per link or per device?