Skip to content

Signal emitting node #585

@Zehir

Description

@Zehir

Just a raw idea for now but here my idea;

Having a signal node that once they got data it's emitting the input value at the end of the generation or now, see below

You will set the signal name but it's would just be a stringname and we will use only one signal because we can't add signal like in -get property list
Like on_data.emit(&"spawn_point", value: Variant) where value is a vector 2.

But when this get triggered ? Because you would expect that this node is connected from the left. So if the neighbor is traverser, check the connected node of there is a signal node to trigger ( in that case the node does not have an output)

Or the node have an input and output and when they are travsered the value is emitted.

And with a optional "differed" option to store the value and emit only at the end of the generation

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions