On Mon, Oct 24, 2011 at 3:22 PM, Ander Conselvan de Oliveira
wrote:
> Em 24-10-2011 18:57, Kristian Høgsberg escreveu:
>>
>> On Mon, Oct 24, 2011 at 9:30 AM, Ander Conselvan de Oliveira
>> wrote:
>>>
>>> wlsc_output_repaint may call wlsc_surface_damage indirectly through
>>> wlsc_output_set_curs
Em 24-10-2011 18:57, Kristian Høgsberg escreveu:
On Mon, Oct 24, 2011 at 9:30 AM, Ander Conselvan de Oliveira
wrote:
wlsc_output_repaint may call wlsc_surface_damage indirectly through
wlsc_output_set_cursor. If this happens in the call made from repaint,
one ends up with repaint being called
On Mon, Oct 24, 2011 at 9:30 AM, Ander Conselvan de Oliveira
wrote:
> wlsc_output_repaint may call wlsc_surface_damage indirectly through
> wlsc_output_set_cursor. If this happens in the call made from repaint,
> one ends up with repaint being called from both idle_repaint and
> wlsc_output_finish
wlsc_output_repaint may call wlsc_surface_damage indirectly through
wlsc_output_set_cursor. If this happens in the call made from repaint,
one ends up with repaint being called from both idle_repaint and
wlsc_output_finish_frame.
Fix this by setting output->repaint_scheduled to 1 before calling
wl