KhronosGroup / KhronosGroup/glTF-InteractivityGraph-AuthoringTool
Bug: More than one input flow socket can be connected to the same output flow socket
- Dominant language
- TypeScript
- Stars
- 33
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
In this simple graph, only "world" is logged – my expectation is that "hello" and "world" are logged instead:
I could not find details in the spec on what happens when the same output flow socket is connected to multiple input flow sockets. I did find that there's a `flow/sequence` node but would not expect that to be necessary. My understanding is that the one value output can also be connected to multiple value inputs. cc @lexaknyazev, I might have missed a place where that is defined?
```json
{
"nodes": [
{
"type": "event/onStart",
"values": [],
"configuration": [],
"flows": [
{
"id": "out",
"node": 2,
"socket": "in"
},
{
"id": "out",
"node": 1,
"socket": "in"
}
],
"metadata": {
"positionX": "271.7791644049969",
"positionY": "274.00562447450295"
}
},
{
"type": "ADBE/output_console_node",
"values": [
{
"id": "message",
"value": "world",
"type": 7
}
],
"configuration": [],
"flows": [],
"metadata": {
"positionX": "806.8545094544273",
"positionY": "474.4824028307539"
}
},
{
"type": "ADBE/output_console_node",
"values": [
{
"id": "message",
"value": "hello",
"type": 7
}
],
"configuration": [],
"flows": [],
"metadata": {
"positionX": "808.3572132317787",
"positionY": "185.60156250000006"
}
}
],
"variables": [],
"customEvents": [],
"types": [
{
"signature": "bool"
},
{
"signature": "int"
},
{
"signature": "float"
},
{
"signature": "float2"
},
{
"signature": "float3"
},
{
"signature": "float4"
},
{
"signature": "float4x4"
},
{
"signature": "custom",
"extensions": {
"AMZN_interactivity_string": {}
}
}
]
}
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the supplied graph JSON and tracing how the event/onStart node dispatches its two flow connections. Check the relevant flow-socket semantics and specification, then establish whether both console outputs should be logged and capture the resolved behavior in a regression test or documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100