Open mtrberzi opened 9 years ago
I tried reproducing this straight from a schematic -> serialize path and couldn't. After adding a bool attribute to the node type and a bool value to the node value, I got this:
"in_node_name": {
"attributes": {
"inNodeAttr": "Bool"
},
"ports": {
"in_port_name": "digital_in"
}
}
...
"nIN": {
"type": "in_node_name",
"attributes": {
"inNodeAttr": "true"
},
"portAttrs": {
"in_port_name": {}
}
},
But is that in the schematic, or are you invoking the frontend? I think this is a frontend problem.
On Thu, Mar 19, 2015 at 11:16 PM, Max Qitian Chen notifications@github.com wrote:
I tried reproducing this straight from a schematic -> serialize path and couldn't. After adding a bool attribute to the node type and a bool value to the node value, I got this:
"in_node_name": { "attributes": { "inNodeAttr": "Bool" }, "ports": { "in_port_name": "digital_in" } } ... "nIN": { "type": "in_node_name", "attributes": { "inNodeAttr": "true" }, "portAttrs": { "in_port_name": {} } },
— Reply to this email directly or view it on GitHub https://github.com/manifold-lang/manifold-frontend/issues/70#issuecomment-83869617 .
Yeah that was built from the schematic. Just confirming it wasn't a core issue.
For example,
register = primitive node (initialValue: Bool, resetActiveHigh: Bool, resetAsynchronous: Bool, clockActiveHigh: Bool, clock: digitalIn, reset: digitalIn, in: digitalIn) -> (out: digitalOut);
only gets thedigitalIn
anddigitalOut
ports in the schematic, not theBool
attributes.