Closed Raffaello closed 4 years ago
it has been done just the bare basic as a show case
TODO
comment in 72f9bd4850822e6da8bdb1fce59aaca4741b6e34 in #66. cc @Raffaello.at the moment is just using `SDL_USEREVENT`, should be something more specific and unique.
TODO
comment in 72f9bd4850822e6da8bdb1fce59aaca4741b6e34 in #66. cc @Raffaello.since v0.2.2 aim to be thread-safe library
waiting for CI improvement before merging #69
waiting for CI improvement before merging #69
and #72 #73
missing #75
this PR complete v.0.2.2
the thread safety i am still considering... (this could be a ticket itself and honestly it should be a major version change probably.... need to consider it more at the time of writing 🤔 )just for fun can be achieved, but won't be really the point of this lib, each terminal should have a dedicated thread, having multiple threads accessing to the same terminal, doesn't make too much sense too me at the moment, but .....butcould be interesting an use case which each thread might have a dedicated region on the terminal to write output there, (the render of course must be synchronized) ... in this case having the extra guarantee of thread-safe lib might be useful...