summaryrefslogtreecommitdiffstats
path: root/remoting/client
diff options
context:
space:
mode:
authorbrettw@chromium.org <brettw@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2012-08-22 21:47:38 +0000
committerbrettw@chromium.org <brettw@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2012-08-22 21:47:38 +0000
commita0217c5e843358d5dd596bede0fd31c8ff843b14 (patch)
tree1185b8ff2052d1616762908c7a15cab0e74a8572 /remoting/client
parentd0de222385e1f6d262ef880dfb010fa4d70ff2df (diff)
downloadchromium_src-a0217c5e843358d5dd596bede0fd31c8ff843b14.zip
chromium_src-a0217c5e843358d5dd596bede0fd31c8ff843b14.tar.gz
chromium_src-a0217c5e843358d5dd596bede0fd31c8ff843b14.tar.bz2
Add a query function for the scaling feature.
We need to be able to query whether scaling is supported before creating a Graphics2D object so we know which code path to use. This just adds a function to do that checking. I also renamed Graphics2DDev to Graphics2D_Dev for consistency with the other Dev wrapper objects. TEST=none BUG=none Review URL: https://chromiumcodereview.appspot.com/10832428 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@152829 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'remoting/client')
-rw-r--r--remoting/client/plugin/pepper_view.cc2
1 files changed, 1 insertions, 1 deletions
diff --git a/remoting/client/plugin/pepper_view.cc b/remoting/client/plugin/pepper_view.cc
index 446201b..ac95e73 100644
--- a/remoting/client/plugin/pepper_view.cc
+++ b/remoting/client/plugin/pepper_view.cc
@@ -90,7 +90,7 @@ void PepperView::SetView(const pp::View& view) {
// Ideally we would always let Graphics2D scale us, but the output quality
// is lousy, so we don't.
- pp::Graphics2DDev graphics2d_dev(graphics2d_);
+ pp::Graphics2D_Dev graphics2d_dev(graphics2d_);
graphics2d_dev.SetScale(1.0f / view_scale_);
bool result = instance_->BindGraphics(graphics2d_);