diff options
| author | Simon Tatham <anakin@pobox.com> | 2015-10-03 12:28:26 +0100 |
|---|---|---|
| committer | Simon Tatham <anakin@pobox.com> | 2015-10-03 16:07:20 +0100 |
| commit | 41cc7c868f72e3131a3d45e38994e9d473824bd1 (patch) | |
| tree | 4a758b96042d5145ad8e9cb94963bc54c0419b75 | |
| parent | 1b2e4d525f5e5686afdbec09c7b796ff546c6357 (diff) | |
| download | puzzles-41cc7c868f72e3131a3d45e38994e9d473824bd1.zip puzzles-41cc7c868f72e3131a3d45e38994e9d473824bd1.tar.gz puzzles-41cc7c868f72e3131a3d45e38994e9d473824bd1.tar.bz2 puzzles-41cc7c868f72e3131a3d45e38994e9d473824bd1.tar.xz | |
GTK 3 port: don't turn off drawing area double buffering.
I think I did this in GTK2 on the basis that our server-side cache
pixmap was double-buffering enough for us - any puzzle which erased a
big area with a background rectangle and then redrew over the top of
it would do so only on the off-screen pixmap, and the updates would
only be copied to the visible window after it was all done.
In GTK3, I don't think there's any need - this is all the usual way
things are done anyway, as far as I can see. So I've turned this call
back off, at least until I hear of a reason why I need it again.
| -rw-r--r-- | gtk.c | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -2573,7 +2573,7 @@ static frontend *new_window(char *arg, int argtype, char **error) fe->statusbar = NULL; fe->area = gtk_drawing_area_new(); -#if GTK_CHECK_VERSION(2,0,0) +#if GTK_CHECK_VERSION(2,0,0) && !GTK_CHECK_VERSION(3,0,0) gtk_widget_set_double_buffered(fe->area, FALSE); #endif { |