renderer: considerable fixes to repaint logic

This commit is contained in:
vaxerski 2023-10-04 13:39:40 +01:00
parent f8c18ff797
commit 4531717f3e
2 changed files with 4 additions and 2 deletions

View file

@ -157,6 +157,7 @@ void Events::listener_monitorFrame(void* owner, void* data) {
return; // we did not schedule a frame yet to be displayed, but we are tearing. Why render? return; // we did not schedule a frame yet to be displayed, but we are tearing. Why render?
PMONITOR->tearingState.nextRenderTorn = true; PMONITOR->tearingState.nextRenderTorn = true;
PMONITOR->tearingState.frameScheduledWhileBusy = false;
} }
static auto* const PENABLERAT = &g_pConfigManager->getConfigValuePtr("misc:render_ahead_of_time")->intValue; static auto* const PENABLERAT = &g_pConfigManager->getConfigValuePtr("misc:render_ahead_of_time")->intValue;

View file

@ -249,7 +249,8 @@ void Events::listener_commitSubsurface(void* owner, void* data) {
if (pNode->pWindowOwner) { if (pNode->pWindowOwner) {
// tearing: if solitary, redraw it. This still might be a single surface window // tearing: if solitary, redraw it. This still might be a single surface window
const auto PMONITOR = g_pCompositor->getMonitorFromID(pNode->pWindowOwner->m_iMonitorID); const auto PMONITOR = g_pCompositor->getMonitorFromID(pNode->pWindowOwner->m_iMonitorID);
if (PMONITOR->solitaryClient == pNode->pWindowOwner && pNode->pWindowOwner->canBeTorn() && PMONITOR->tearingState.canTear) { if (PMONITOR->solitaryClient == pNode->pWindowOwner && pNode->pWindowOwner->canBeTorn() && PMONITOR->tearingState.canTear &&
pNode->pSurface->wlr()->current.committed & WLR_SURFACE_STATE_BUFFER) {
CRegion damageBox; CRegion damageBox;
wlr_surface_get_effective_damage(pNode->pSurface->wlr(), damageBox.pixman()); wlr_surface_get_effective_damage(pNode->pSurface->wlr(), damageBox.pixman());