And the whole damage handling could be improved here, but without the cScreen->damageScreen (); call it is already acting much more sane, but it has some room for optimization still (no need to damage the region twice for example)...
« Back to merge proposal
And the whole damage handling could be improved here, but without >damageScreen (); call it is already acting much more
the cScreen-
sane, but it has some room for optimization still (no need to damage
the region twice for example)...