diff options
| author | ben@chromium.org <ben@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-02-11 20:16:45 +0000 |
|---|---|---|
| committer | ben@chromium.org <ben@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-02-11 20:16:45 +0000 |
| commit | 861f238313d2b2842dc90415e3b394addd5c3872 (patch) | |
| tree | 3c56336f4b41876b8b5c4e4827c1c2d64dd2a412 /views/examples/combobox_example.h | |
| parent | 6a1ae6cdf8f1edfb89f5f2ce823af937f7f43aa9 (diff) | |
| download | chromium_src-861f238313d2b2842dc90415e3b394addd5c3872.zip chromium_src-861f238313d2b2842dc90415e3b394addd5c3872.tar.gz chromium_src-861f238313d2b2842dc90415e3b394addd5c3872.tar.bz2 | |
Safer KeyEvent construction using synthetic MSGs.
After talking to jar, it seems impossible to reliably get a reasonable MSG from Windows given native nested message loops etc. So I am making this do what my prototype did and just generate a synthetic MSG from the information supplied to the WndProc. It turns out this is what ATL does too for its GetCurrentMessage implementation.
BUG=none
TEST=none
Review URL: http://codereview.chromium.org/6500003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@74654 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'views/examples/combobox_example.h')
0 files changed, 0 insertions, 0 deletions