BDisp
BDisp
@tznind please try with the PR #3768 and let me know what do you think. You can use it on all drivers to check if sixel is supported at least....
Please @tznind with tis PR #3770 can you test `Sixel` in the `CursesDriver`. Thanks.
That's great. Is the first video using `WindowsDriver`?
Can you please try in the `CursesDriver` using my PR #3770? You can the same code as you used for the `NetDriver`.
> ...cause things to be redrawn, but the only thing that actuallyi gets changed are attributes. > > This points to another bug in either `AddString` or `OutputImpl.Write` regarding writing...
I'm posting this here because I'm not sure if it's related to the same problem. Glyphs disappear when moving the Dialog. If it is not the same problem, please create...
Only WindowsDriver send their own events. FYI UnixDriver isn't CursesDriver and doesn't have anything of ncurses library and the mouse event is pure native escape sequences as the DotnetDriver.
Without a doubt, option 1 should be considered, allowing MouseInterpreter to perform the necessary procedure for all drivers.
Here my opinion on this. `View` class has a `Data` property which is for the user use it as he like. We should avoid use this property internally and only...
> But, to be clear, Designer is NOT part of the library and should be able to use it as it see fits. Yes, I know. I only was asking...