Balázs Cene

Hmm, I don't really see what the issue could be then. It's even more annoying that it's terminal specific! What happens if you insert the line `terminal.flush()` above the report...

@stewartad Now that's fascinating! Just to confirm, the PyPi version exhibits the issue for you, but the GitHub one doesn't? Out of curiosity, which terminal emulator do you use?

So it seems to be a VTE-specific issue where disabling both events at the same time causes only one of them to fully disable? Now that I look at it...

@treamology Could you test out the latest commit? Using just `1003` seems to work fine, though I've never been able to recreate the issue so can't comment on that.

> Actually, looking at [context_managers.py:148](https://github.com/bczsalba/pytermgui/blob/ba75eeadbffba948ffb046a353e6be5d01a067c7/pytermgui/context_managers.py#L148), it seems like the actual problem is that it's referencing the event variable without being inside a for loop. event remains set to the last...

Sorry about the wait, not sure how I forgot about this one.

This issue is related to #81, so the note I left there is relevant here as well. There _is_ a way to do this better (specifically diff-based screen updates), but...

While we have made some progress towards helping with this, unfortunately the ideal solution (at least from what I found, implemented in shade40's [slate](https://github.com/shade40/Slate/blob/5ea61e7ca248756b479a818ec3df5f004a7bea3d/slate/screen.py#L127)) requires PTG's core to be uprooted...

Forgot to close this, but the new docs have been up for a while now and they should fix all of these issues. Thanks for the shout!

The current state of the library doesn't really fly with this idea unfortunately. Splitters are too finicky to make work, and baking a custom widget for this is ugly. Thank...