Filled in missing dmSize, dmDriverExtra values for EnumDisplaySettings call

Filled in missing dmSize, dmDriverExtra values for EnumDisplaySettings call

These values should be filled in as specified by the MSDN documentation for the function: http://msdn.microsoft.com/en-us/library/windows/desktop/dd162611(v=vs.85).aspx

BUG=418684
TBR=kbr@chromium.org

Committed: https://crrev.com/b3b81dc60c55b48d2f49c8785914ed9acfb485e0
Cr-Commit-Position: refs/heads/master@{#297320}

[bajones, 2014-09-29 23:45:33]

bajones@chromium.org changed reviewers:
+ kbr@chromium.org

[bajones, 2014-09-29 23:45:42]

The CQ bit was checked by bajones@chromium.org

[commit-bot: I haz the power, 2014-09-29 23:46:57]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/613033002/1

[commit-bot: I haz the power, 2014-09-30 00:50:51]

Committed patchset #1 (id:1) as 54177b1cb487327b7ed3b6e1e70c805b8e5b184f

[commit-bot: I haz the power, 2014-09-30 00:51:48]

Patchset 1 (id:??) landed as
https://crrev.com/b3b81dc60c55b48d2f49c8785914ed9acfb485e0
Cr-Commit-Position: refs/heads/master@{#297320}

[Ken Russell (switch to Gerrit), 2014-09-30 01:35:11]

Yikes. LGTM

We really need to figure out how to unit test this platform-dependent code.

[bajones, 2014-09-30 01:56:08]

On 2014/09/30 at 01:35:11, kbr wrote:
> Yikes. LGTM
> 
> We really need to figure out how to unit test this platform-dependent code.

Agreed, though I'm not sure how I could have caught this oversight with a test.
The function was performing correctly without these sizes set (which was
probably just because they happened to be initializing to 0).

[Ken Russell (switch to Gerrit), 2014-09-30 02:39:02]

On 2014/09/30 01:56:08, bajones wrote:
> On 2014/09/30 at 01:35:11, kbr wrote:
> > Yikes. LGTM
> > 
> > We really need to figure out how to unit test this platform-dependent code.
> 
> Agreed, though I'm not sure how I could have caught this oversight with a
test.
> The function was performing correctly without these sizes set (which was
> probably just because they happened to be initializing to 0).

They almost certainly contained uninitialized information which would have blown
up at some point.