Vladimir Sibirov
Vladimir Sibirov
That's actually expected behaviour. In order to get all packets from the buffer you need to use `input.hasStream()` and `input.getStream()`, or a loop over items using `input.has()` and `input.get()`.
There is no benefit, it's a design tradeoff. Firing patterns in FBP are not always easy. There might be a corner case like this, and components have to take it...
Mea culpa, I forgot that control ports in NoFlo don't fire. Then, indeed, it makes sense to do what @bergie suggested.
This only makes sense once all the consumers use brackets properly (i.e. for streams instead of objects), until then it's gonna mess the data flows and affect performance badly. Thus,...
@forresto As a quick fix that would be acceptable in a short term and #241 exists for that. But in long-term we need to avoid CS stubs or at least...
@forresto My thoughts, exactly! @jpaulm, @oleksandr What do you think?
Bumping this one as it's still pretty relevant.
I agree with @jonnor that it should have nothing to do with fbp-spec. All that is to be known about these "prototype components" is their name, inports and outports. So...
A minor thing: to speed up prototyping even more, it would be nice if the tool added `IN` and `OUT` ports as default, so that you could begin prototyping a...
@IainShigeoka This workaround helped, thank you!