every time write a char or something change the terminal status, dispatch an event to represent need updates.
so it could be done in an async mode.
how many if it is already pushed an event update, should send multiple for every single char? the render will just render the last one...
so i will say it will just raise a flag more then publish an event per se.
so multiple chnages without render will be just a flag send to the queue and doesnt publish anything else unless the "internal" flag was updated=true for eg....
this put also redundant the fact of the event pushing to sdl but it might be smoother for the event loop....
also the term handler function could just handle its own events automatically....
for sure require a flag to enable/disable this new feature.
it can just start with disabled.
every time write a char or something change the terminal status, dispatch an event to represent need updates.
so it could be done in an async mode.
how many if it is already pushed an event update, should send multiple for every single char? the render will just render the last one...
so i will say it will just raise a flag more then publish an event per se.
so multiple chnages without render will be just a flag send to the queue and doesnt publish anything else unless the "internal" flag was updated=true for eg....
this put also redundant the fact of the event pushing to sdl but it might be smoother for the event loop....
also the term handler function could just handle its own events automatically....
for sure require a flag to enable/disable this new feature. it can just start with disabled.