"Fork-join" model fits pretty well for several async animations (you can spawn a lot of flow in parallel), but there is no "wait for flow" api in module. I came up with code like this, but there is probably better way to implement such functionality.

local function flow_wait_others(flows)
	assert(flows)

	-- single coroutine
	if flow.co then
		flow.until_true(function(args)
			return coroutine.status(flow.co) == "dead"
		end)
		return
	end

	-- several coroutines
	for k, v in pairs(flows) do
		flow.until_true(function(args)
			return coroutine.status(v.co) == "dead"
		end)
	end
end

In debugging, I found the order of execution when using Flow was a little unexpected. It might be worth documenting.

For example, in an Update function (not real code):

• print("testA")
• flow( print("testB") ) -- no delay before calling print
• print("testC")

I was expecting it to print testA, testB, testC. Instead it's testA, testC, testB. They're all executed on the same frame, but Flow executes later.

This is totally fine but might be worth noting somewhere.

Also, thanks for the great toolset, and all your assets really.

In example written:
log1.level(logger.WARN)
But must be
logger.level(logger.WARN)
Because created log instance have no level function. This function is only available in the entire module.
Links:
logger.lua
logger.md - mistake is here

I have two scripts that post messages each other. Scripts' on_message functions look ugly and unreadable so I decided to rework them using flow.

My old code usually posts and receives a few dozens messages in a single frame.

I found that flow.until_message waits for next frame after receiving the message. Therefore my new code requires a few dozens frames to complete --- this is too long for my game.

Is it a flaw by design? Can it be fixed? flow makes code look so much readable...

If we reload collection with gui elements and use simple_input lib in scripts we got an error:

ERROR:SCRIPT: /ludobits/m/simple_input.lua:65: Node used in the wrong scene
stack traceback:

It just because local registered_nodes = {} is local table and not cleaning after closing the old collection. Elements in this table has the same url but not correct node.
So we need call unregister for all registered element in final method or what is better need to method unregisterAll.

After update, flow.gui_animate was broken
You can only access gui.* functions and values from a gui script instance (.gui_script file)
Is it issue from instance remove from 151 update?

I've fallen in love with coroutines through use of Sequence.

I realised that errors in Sequence weren't thrown as normal - with some research I now understand why: https://forum.defold.com/t/defold-doesnt-show-any-error-and-stop-execution-of-the-oroutine-if-you-wrongly-send-message-from-module-msg-post-solved/3441/10

Would it be possible to make Sequence throw errors? Doesn't look like errors are being caught currently and I'm not sure what to do to change that.

The function savetable.save() creates unreadable files on my Windows 10 computer, see attached image.
I have also attached the file.

This problem does not happen in the older version 6.7.1

savetable.zip

In flow module while creating new instance of timer you use 0.016 delay.

After a little test:

init function:

timer.delay(0.016, true, function(self, handler, dt)
  timer_time = timer_time + dt
  print('timer: ' .. timer_time)
end)

update function:

update_time = update_time + dt
print('update: ' .. update_time)

The difference between timer_time and update_time keeps growing:

In other modules you using timer.delay(0... and in this case the gap is gone:

Can you add an "break" function to the flow?

flow.load can be used for collection proxy.

Does this work with collection factory too?

Thanks.