From dfab86df5e278ce77f0df86b7f2cf359e9456b2d Mon Sep 17 00:00:00 2001 From: Carsten Haitzler Date: Wed, 26 Sep 2012 13:23:29 +0000 Subject: [PATCH] and back to full update - poo. SVN revision: 77093 --- legacy/evas/src/modules/engines/gl_x11/evas_engine.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/legacy/evas/src/modules/engines/gl_x11/evas_engine.c b/legacy/evas/src/modules/engines/gl_x11/evas_engine.c index 191baac327..8f41290907 100644 --- a/legacy/evas/src/modules/engines/gl_x11/evas_engine.c +++ b/legacy/evas/src/modules/engines/gl_x11/evas_engine.c @@ -776,12 +776,14 @@ eng_setup(Evas *e, void *in) // to either swap or copy backbuffer and front buffer, but strictly that is // not true. technically backbuffer content is totally undefined after a swap // and thus you MUST re-render all of it, thus MODE_FULL -// re->mode = MODE_FULL; + re->mode = MODE_FULL; // BUT... reality is that lmost every implementation copies or swaps so // triple buffer mode can be used as it is a superset of double buffer and // copy (though using those explicitly is more efficient). so let's play with // triple buffer mdoe as a default and see. - re->mode = MODE_TRIPLE; +// re->mode = MODE_TRIPLE; +// XXX: note - the abvoe seems to break on some older intel chipsets and +// drivers. it seems we CANT depend on backbuffer staying around. bugger! } if (!re->win) {