aura: Fix "not-allowed" cursor and hot-points of some other cursors.

ui/aura/root_window_host_linux.cc

Index: ui/aura/root_window_host_linux.cc
diff --git a/ui/aura/root_window_host_linux.cc b/ui/aura/root_window_host_linux.cc
index 9cdef7c07418010704470f472f9c032d3aca53be..fc6934d99a26b47b892fede9babae0c0a1064977 100644
--- a/ui/aura/root_window_host_linux.cc
+++ b/ui/aura/root_window_host_linux.cc
@@ -323,10 +323,11 @@ class RootWindowHostLinux::ImageCursors {
     UnloadAll();
     // The cursor's hot points are defined in chromeos's
     // src/platforms/assets/cursors/*.cfg files.

[sky, 2012/07/23 23:00:57]

Is there some better way to communicate this so that it isn't possible for
chromeos and chrome to get out of sync?

[varunjain, 2012/07/25 16:38:28]

Actually this is inaccurate. We have new cursor images from Alex with hot points
shown in the image. I have updated the comment. I think best way to do this
would be to define hot points in cfg files checked in where the cursor images
are (ui/resources/aura). If you think thats ok, I can do that in a followup CL.
My concerns was if its worth increasing the resources just for the hot points.

-    LoadImageCursor(ui::kCursorNull, IDR_AURA_CURSOR_PTR, 9, 5);
-    LoadImageCursor(ui::kCursorPointer, IDR_AURA_CURSOR_PTR, 9, 5);
-    LoadImageCursor(ui::kCursorNoDrop, IDR_AURA_CURSOR_NO_DROP, 9, 5);
-    LoadImageCursor(ui::kCursorCopy, IDR_AURA_CURSOR_COPY, 9, 5);
+    LoadImageCursor(ui::kCursorNull, IDR_AURA_CURSOR_PTR, 8, 3);
+    LoadImageCursor(ui::kCursorPointer, IDR_AURA_CURSOR_PTR, 8, 3);
+    LoadImageCursor(ui::kCursorNoDrop, IDR_AURA_CURSOR_NO_DROP, 5, 4);
+    LoadImageCursor(ui::kCursorNotAllowed, IDR_AURA_CURSOR_NO_DROP, 5, 4);
+    LoadImageCursor(ui::kCursorCopy, IDR_AURA_CURSOR_COPY, 5, 5);
     LoadImageCursor(ui::kCursorHand, IDR_AURA_CURSOR_HAND, 9, 4);
     LoadImageCursor(ui::kCursorMove, IDR_AURA_CURSOR_MOVE, 12, 12);
     LoadImageCursor(ui::kCursorNorthEastResize,