Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

x/exp/shiny/driver/x11driver: implement back buffer #15181

Open
eaburns opened this issue Apr 7, 2016 · 2 comments

Comments

Projects
None yet
5 participants
@eaburns
Copy link

commented Apr 7, 2016

Please answer these questions before submitting your issue. Thanks!

  1. What version of Go are you using (go version)?

1.6

  1. What operating system and processor architecture are you using (go env)?
$ go env 
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/eaburns"
GORACE=""
GOROOT="/home/eaburns/src/go.googlesource.com/go"
GOTOOLDIR="/home/eaburns/src/go.googlesource.com/go/pkg/tool/linux_amd64"
GO15VENDOREXPERIMENT="1"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0"
CXX="g++"
CGO_ENABLED="1"
  1. What did you do?

Use shiny x11driver

  1. What did you expect to see?

Double buffering.

  1. What did you see instead?

No double buffering.

@gopherbot

This comment has been minimized.

Copy link

commented Apr 7, 2016

CL https://golang.org/cl/21660 mentions this issue.

@nigeltao

This comment has been minimized.

Copy link
Contributor

commented Apr 8, 2016

This is indeed a bug in the x11driver code, but it was a known issue: the code already had a "TODO: implement a back buffer" comment. FWIW, my personal opinion is that it wasn't necessary to file a new issue, even if you've just followed it up with a CL that says "Fixes #15181", as it would have sufficed to delete the TODO.

@bradfitz bradfitz added this to the Unreleased milestone Apr 9, 2016

@dmitshur dmitshur changed the title shiny/driver/x11driver: implement back buffer x/exp/shiny/driver/x11driver: implement back buffer Mar 10, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.