Community
Participate
Working Groups
Always true, so we can remove USE_DOUBLE_BUFFER=true in BufferedCanvas
New Gerrit change created: https://git.eclipse.org/r/c/platform/eclipse.platform.team/+/176933
Nikita, the whole class org.eclipse.compare.internal.BufferedCanvas is really old. Do you know if this double-buffering is still useful for modern SWT applications or can we simply replace it with a regular Canvas?
(In reply to Lars Vogel from comment #2) > Nikita, the whole class org.eclipse.compare.internal.BufferedCanvas is > really old. Do you know if this double-buffering is still useful for modern > SWT applications or can we simply replace it with a regular Canvas? macOS and GTK will double-buffer automatically, Windows needs SWT.DOUBLE_BUFFERED widget style to be specified explicitly. So, BufferedCanvas should be replaced with Canvas(parent, SWT.DOUBLE_BUFFERED | ...)
Thanks Nikita. Would it be possible to activate double buffering in Windows by default?
(In reply to Lars Vogel from comment #4) > Thanks Nikita. > > Would it be possible to activate double buffering in Windows by default? This will reduce painting performance for widgets that don't need it, for example, if all a widget does is paint an image, it doesn't need buffering. Also, advanced graphics on Windows (GDI+) are implicitly buffered. Forcing SWT.DOUBLE_BUFFERED will be even more wasteful in this case.
Thanks for the clarification, Nikita. Sounds like we should not change the win default.
Gerrit change https://git.eclipse.org/r/c/platform/eclipse.platform.team/+/176933 was merged to [master]. Commit: http://git.eclipse.org/c/platform/eclipse.platform.team.git/commit/?id=cee65979a07f1df261572ed31930e458a4140372
Thanks Nikita, I opened Bug 571954 for the complete replacement.