Repository navigation
Defer cursor redrawing when writing buffer - #2960
Dustin L. Howett (MSFT) (DHowett-MSFT) merged 1 commit into
Conversation
|
To take this further, if we know there will be more |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Mike Griese (zadjii-msft)
left a comment
There was a problem hiding this comment.
This seems reasonable to me. I'd definitely want Michael Niksa (@miniksa)'s thoughts though to be sure
|
You will probably need to merge in |
7dc6179 to
3d42d9d
Compare
| auto& cursor = _buffer->GetCursor(); | ||
| const Viewport bufferSize = _buffer->GetSize(); | ||
|
|
||
| cursor.StartDeferDrawing(); |
There was a problem hiding this comment.
Leave behind the comment explaining why this is required (for performance reasons, we can not waste time displaying a cursor event when we know more text is coming right behind it).
Michael Niksa (miniksa)
left a comment
There was a problem hiding this comment.
I'm fine with this. It looks like (in historical spelunking of our code) that some of the stream writing methods used to hide the cursor for the same reasons and it was lost to the sands of time.
3d42d9d to
7c6bf96
Compare
|
Thanks for the contribution! |
|
π Handy links: |
|
Thank you for the great job so far. Don't know if it refers to this specific topic, but I'm running ntop in PowerShell and even in the new release (Version: 0.6.2951.0) I can see the cursor jumping up and down the screen while the screen gets refreshed. Shouldn't this be fixed by this pull request? |
|
Sorta. You're more likely being impacted by #3093 π |
Summary of the Pull Request
Defer cursor redrawing when reading buffer
References
#2932
PR Checklist
Detailed Description of the Pull Request / Additional comments
My previous PR #2932 introduces an overhead when writing a lot of text on screen. I found that this could be optimized by delaying cursor redraw
Validation Steps Performed