You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While one can add non Window containers to the Layout, apparently the design forces the children to be Window objects. I believe this is a little artificial limitation. The Window implementation provides great features, in some edge cases it shows it's limitations. I know that technically I can override all the Container abstract methods, but semantically that would be a little mess.
In my particular case I want to handle fast logginng scrolling into a window and different text formatting mechanism.
Some other enhancement suggestions:
The _Split window_to_small could/should be also of type Callable. The information could be used somewhere else, including logging, or displaying it in a dedicated space on the screen
Saw several issues with wishes to be able to write_raw to the terminal (through screen). While one could always write directly to the stdout the escape sequences, that would bypass the normal rendering flow. I know the powerfull screen diffing mechanism, but again for my "fast scrolling" interface and other purposes I would like to bypass the diff for the region of my "renderable". I guess the simplest solution would be when doing the diff for a line to look into an "exception dict" if there is an entry for that line, if yes, check if the current character position is in any of the ranges for that entry. If yes, just call write_raw. I know that technically I could use the ZeroWdithEscape buffer, but again semantically would be a hack.
I know this might create some headache for you as it may mess up the screen and produce unwanted issues, but that would be the responsability of the user to add to the "exception ranges dict"
Another use-case would be a terminal emulator inside a PT appication like ptterm. Converting the escape sequences to fragments and then back to raw is a bit of overhead, especially if you want again, fast scrolling inside the virtual terminal.
Thanks,
Z
The text was updated successfully, but these errors were encountered:
While one can add non Window containers to the Layout, apparently the design forces the children to be Window objects. I believe this is a little artificial limitation. The Window implementation provides great features, in some edge cases it shows it's limitations. I know that technically I can override all the Container abstract methods, but semantically that would be a little mess.
In my particular case I want to handle fast logginng scrolling into a window and different text formatting mechanism.
Some other enhancement suggestions:
I know this might create some headache for you as it may mess up the screen and produce unwanted issues, but that would be the responsability of the user to add to the "exception ranges dict"
Another use-case would be a terminal emulator inside a PT appication like ptterm. Converting the escape sequences to fragments and then back to raw is a bit of overhead, especially if you want again, fast scrolling inside the virtual terminal.
Thanks,
Z
The text was updated successfully, but these errors were encountered: