Skip to content

dynamic datatype feature #498

@cxxamz

Description

@cxxamz

Your idea

In my other project, I use unconnected input and output ports found during the scanning process as the module's input and output ports. This way, ports that are already connected cannot serve as module output ports. My solution is to add a node whose input and output types are the same, which allows for an additional output port. However, currently, port types are fixed, and different types require creating different nodes, which makes the workload very large and difficult to expand. Dynamic port types are the approach I am currently considering.

With dynamic data type feature, we don't have to define a new node for each type, in the following usage scenarios.

demo - https://github.com/cxxamz/nodeeditor/tree/feature/dynamic_datatype

11-33-10.mp4

Image.

Problem to be solved

None.

Prior art

No response

Additional context

No response

Checklist

  • I have verified that this feature request has not been logged before, by searching the issue tracker for similar requests

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions