Remaining bits to get views_examples_with_content_exe to work on Mac

ui/gfx/mac/point_utils.mm

Index: ui/gfx/mac/point_utils.mm
diff --git a/ui/gfx/mac/point_utils.mm b/ui/gfx/mac/point_utils.mm
new file mode 100644
index 0000000000000000000000000000000000000000..df67fe9b588a81ed13c28b57b777adb258ece158
--- /dev/null
+++ b/ui/gfx/mac/point_utils.mm
@@ -0,0 +1,44 @@
+// Copyright 2014 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#import "ui/gfx/mac/point_utils.h"
+
+#import <Cocoa/Cocoa.h>
+
+#include "ui/gfx/geometry/point.h"
+#include "ui/gfx/geometry/rect.h"
+
+namespace gfx {
+
+namespace {
+
+CGFloat PrimaryDisplayHeight() {
+  return NSMaxY([[[NSScreen screens] objectAtIndex:0] frame]);

[Andre, 2014/06/04 23:55:08]

How about multiple screens?

[tapted, 2014/06/11 07:38:00]

screen coordinates are always relative to the bottom left of the screen[0],
which is the screen with the menu bar on it. 

screen_mac.mm actually has something like this (ConvertCoordinateSystem) in a
private namespace. It's possible we won't need point_utils.mm .... I keep
finding reasons to say "don't really need to use it here" ;)

+}
+
+}  // namespace
+
+NSPoint ScreenPointToNSPoint(const gfx::Point& point) {
+  return NSMakePoint(point.x(), PrimaryDisplayHeight() - point.y());
+}
+
+gfx::Point ScreenPointFromNSPoint(const NSPoint& point) {
+  return gfx::Point(point.x, PrimaryDisplayHeight() - point.y);
+}
+
+NSRect ScreenRectToNSRect(const gfx::Rect& rect) {
+  return NSMakeRect(rect.x(),
+                    PrimaryDisplayHeight() - rect.y() - rect.height(),
+                    rect.width(),
+                    rect.height());
+}
+
+gfx::Rect ScreenRectFromNSRect(const NSRect& rect) {
+  return gfx::Rect(rect.origin.x,
+                   PrimaryDisplayHeight() - rect.origin.y - rect.size.height,
+                   rect.size.width,
+                   rect.size.height);
+}
+
+}  // namespace gfx