[Bug] using ush_print multiple times successively only prints the last command issued
cosmikwolf opened this issue · 2 comments
Pretty self explanatory, using ush_print multiple times successively only prints the last command issued.
It's not a bug, it's a feature :)
Real printing doesn't take place in the ush_print.
This is only a non-blocking "request" to print something without queuing anything (or only 1 request queue size).
Printing multiple data in one response need implement fsm or big buffer on the application side.
This limitation drastically lowers the complexity and resources usage.
I get it now! I did not realize it was a whole FSM built in.
It took me a bit, but I figured it out! Some documentation or hints on how to use the FSM in the readme would have made things more clear, but I was able to figure it out after staring at it for a while :D