Updated drag-and-drop assets.

Updated drag-and-drop assets.

This patch updates icons for dragging, especially used in Files.app.

TEST=Enter Files.app, drag and drop.
BUG=137982
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=187635

[mtomasz, 2013-03-11 06:58:36]

@oshima: PTAL.

[oshima, 2013-03-11 10:29:57]

do they have the same hot point?

[mtomasz, 2013-03-11 10:45:35]

On 2013/03/11 10:29:57, oshima wrote:
> do they have the same hot point?

What do you mean by term hot point?

[oshima, 2013-03-11 11:03:41]

Each pointer image has its own point that is used to identify where it is
pointing to within the image ( [1,3] in 32x32 image, for example).
See ash/wm/image_cursors.cc


On Mon, Mar 11, 2013 at 3:45 AM, <mtomasz@chromium.org> wrote:

> On 2013/03/11 10:29:57, oshima wrote:
>
>> do they have the same hot point?
>>
>
> What do you mean by term hot point?
>
>
https://codereview.chromium.**org/12766002/<https://codereview.chromium.org/1...
>

[mtomasz, 2013-03-11 13:31:44]

Fixed the hot points. However, I am confused about the comment in the
image_cursors.cc. Are the hot points embedded or not? The provided link says it
is WontFix. Please clarify.

[oshima, 2013-03-11 16:34:43]

We still want to move this into png file.
It was just put on hold.

https://codereview.chromium.org/12766002/diff/9001/ash/wm/image_cursors.cc
File ash/wm/image_cursors.cc (right):

https://codereview.chromium.org/12766002/diff/9001/ash/wm/image_cursors.cc#ne...
ash/wm/image_cursors.cc:37: {ui::kCursorNotAllowed, IDR_AURA_CURSOR_NO_DROP, {9,
9}, {18, 18}},
does this change means the image has already been updated but the hot point
wasn't? Just want to make sure this change is intentional and good.

[mtomasz, 2013-03-12 01:19:17]

https://codereview.chromium.org/12766002/diff/9001/ash/wm/image_cursors.cc
File ash/wm/image_cursors.cc (right):

https://codereview.chromium.org/12766002/diff/9001/ash/wm/image_cursors.cc#ne...
ash/wm/image_cursors.cc:37: {ui::kCursorNotAllowed, IDR_AURA_CURSOR_NO_DROP, {9,
9}, {18, 18}},
On 2013/03/11 16:34:43, oshima wrote:
> does this change means the image has already been updated but the hot point
> wasn't? Just want to make sure this change is intentional and good.

kCursorNoDrop and kCursorNotAllowed is the same asset: IDR_AURA_CURSOR_NO_DROP.

[oshima, 2013-03-12 01:27:47]

ah i see. Thank you for clarification. lgtm.

[commit-bot: I haz the power, 2013-03-12 02:03:39]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/mtomasz@chromium.org/12766002/9001

[commit-bot: I haz the power, 2013-03-12 02:03:43]

Presubmit check for 12766002-9001 failed and returned exit status 1.

INFO:root:Found 5 file(s).

Running presubmit commit checks ...
Running /b/commit-queue/workdir/chromium/PRESUBMIT.py
Running /b/commit-queue/workdir/chromium/ash/PRESUBMIT.py
Running /b/commit-queue/workdir/chromium/ash/resources/PRESUBMIT.py

** Presubmit ERRORS **
Missing LGTM from an OWNER for these files:
    ash/wm/image_cursors.cc

[mtomasz, 2013-03-12 09:51:05]

@sky: I need you OWNERS lgtm. Already reviewed by @oshima.

[sky, 2013-03-12 14:32:19]

LGTM

[commit-bot: I haz the power, 2013-03-12 14:42:08]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/mtomasz@chromium.org/12766002/9001

[commit-bot: I haz the power, 2013-03-12 20:09:34]

Change committed as 187635

[mtomasz, 2013-03-15 08:11:15]

On 2013/03/12 20:09:34, I haz the power (commit-bot) wrote:
> Change committed as 187635

Nah, again the assets were not copied. @oshima: Do you have an idea, why the
assets has not been commited?

[oshima, 2013-03-15 11:07:28]

On 2013/03/15 08:11:15, mtomasz wrote:
> On 2013/03/12 20:09:34, I haz the power (commit-bot) wrote:
> > Change committed as 187635
> 
> Nah, again the assets were not copied. @oshima: Do you have an idea, why the
> assets has not been commited?

CQ can't commit binary files. Please commit them manually.