Rob Mayer

I've been racking my brain on how to fix this, but I can't seem to grok it - anyone have an PR for this?

the "Buffer" component, illustrating the forced "isCyclic" flag `{ "name": "BUF", "creationIndex": 6, "colour": { "r": 0.7641509771347046, "g": 0.40998053550720217, "b": 0.19103774428367616, "a": 1.0 }, "nameColour": { "r": 1.0, "g": 1.0,...

An interesting side-effect of this BUF object.  This output will be delayed by 4 "ticks" from the input.

I think I figured out why. the "flow" of a powering on propagates each tick, but the cutting of power is immediate. in other words your clock has the power...

cutting the clock speed in half seems to work better as a clock because of the delayed-on but instant-off issue. 

Even more fun with this little hacked component: a rising and falling edge detector: RISING goes high for one tick when IN goes high FALLING stays high except for one...

+1 for a 4, 8, 16, and 32 bit bus cable :)

same issue here. in @scoped/somelib somelib/ > yarn link success use yarn link "@scoped/somelib" someproject/ > yarn link "@scoped/somelib" success using linked package someproject/ > yarn install can't find "@scoped/somelib"...

throwing in a plea for some kind of "onCommit", "onChangeComplete" or similar that utilizes the native change event. obviously one could trivially add a custom handler using the addEventListener, but...

that's fair on the domes. the use case for the reverse 3 way adapter is primarily for space stations and large built-in-space vessels.