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
Hi there, I know this isn't an issue, but I was trying to read the source and it was difficult to understand how smart/fastCSR works. AFAICT, CSR changes the region based on the terminal rows, which means that scroll up and down should affect everything from col: 0 to col: term.width.
However, the test examples where a screen node was created as a parent to a box / scrollable box, we have a region that is getting scrolled but the surrounding area is not. I was hoping to be pointed to the area of code that implements this to know how this black magic sorcery is being done.
Thanks!
The text was updated successfully, but these errors were encountered:
Hi there, I know this isn't an issue, but I was trying to read the source and it was difficult to understand how smart/fastCSR works. AFAICT, CSR changes the region based on the terminal rows, which means that scroll up and down should affect everything from col: 0 to col: term.width.
However, the test examples where a screen node was created as a parent to a box / scrollable box, we have a region that is getting scrolled but the surrounding area is not. I was hoping to be pointed to the area of code that implements this to know how this black magic sorcery is being done.
Thanks!
The text was updated successfully, but these errors were encountered: