Crossterm backend not properly flushing after print

[MichaelMackus]

The crossterm backend doesn't appear to be properly flushing after calls to print. The issue is due to partial updates not flushing the stdout output stream. The bug occurs linux, perhaps it doesn't apply to all systems.

I've submitted a PR with a fix. You can also workaround the bug by calling stdout().flush().expect("Command fail"); in your tick function (although that will only flush the previous frame's buffer I believe, since the actual output happens after the call to tick).

[sdsalyer]

I have similar issue with Crossterm, but the stdout().flush() suggested in the tick() function didn't help.

I get the below error and have to reset the terminal after.

    Finished `dev` profile [unoptimized + debuginfo] target(s) in 16.34s
     Running `target/debug/rogu`

thread 'main' panicked at /home/berts/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/bracket-terminal-0.8.7/src/hal/crossterm_be/main_loop.rs:229:31:
                               index out of bounds: the len is 4216 but the index is 6076
                                                                                         note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

EDIT:

I think my issue is related to using simple80x50 but the terminal size is 124 x 32 (or any other size that isn't the same dimensions). The crossterm main_loop uses the minimum of these values, and then hits the index out of bounds attempting to access a buffer index that's out of bounds.

Supplying the exact dimensions avoids the issue -- but exiting the program with Ctl-C does not reset the background color .