Searched refs:WM_CLOSE (Results 1 - 12 of 12) sorted by relevance
| /external/webrtc/webrtc/base/ |
| H A D | win32window.cc | 80 case WM_CLOSE:
|
| /external/lzma/CPP/Windows/Control/ |
| H A D | Window2.cpp | 153 case WM_CLOSE:
|
| /external/vulkan-validation-layers/demos/smoke/ |
| H A D | ShellWin32.cpp | 194 case WM_CLOSE:
|
| /external/webrtc/talk/media/devices/ |
| H A D | gdivideorenderer.cc | 131 // created by another thread. Instead, we send WM_CLOSE message.
133 SendMessage(handle(), WM_CLOSE, 0, 0); local
|
| /external/icu/icu4c/source/samples/layout/ |
| H A D | clayout.c | 323 SendMessage(hwnd, WM_CLOSE, 0, 0);
|
| H A D | layout.cpp | 319 SendMessage(hwnd, WM_CLOSE, 0, 0);
|
| /external/libchrome/base/message_loop/ |
| H A D | message_loop_unittest.cc | 950 PostMessage(hwnd, WM_CLOSE, 0, 0);
957 if (message == WM_CLOSE)
986 // If this message is a WM_CLOSE, explicitly exit the modal loop. Posting
989 if (msg.message == WM_CLOSE)
|
| /external/chromium-trace/catapult/telemetry/telemetry/internal/platform/ |
| H A D | win_platform_backend.py | 425 # It seems safest to send the WM_CLOSE messages after discovering
439 win32gui.SendMessage(hwnd, win32con.WM_CLOSE, 0, 0)
|
| /external/webrtc/webrtc/examples/peerconnection/client/ |
| H A D | main_wnd.cc | 383 case WM_CLOSE:
|
| /external/vulkan-validation-layers/demos/ |
| H A D | cube.c | 1924 case WM_CLOSE:
|
| H A D | tri.c | 1525 case WM_CLOSE:
|
| /external/eclipse-basebuilder/basebuilder-3.6.2/org.eclipse.releng.basebuilder/plugins/ |
| H A D | org.eclipse.swt.win32.win32.x86_3.6.1.v3657a.jar | META-INF/MANIFEST.MF META-INF/ECLIPSEF.SF META-INF/ECLIPSEF.RSA META ... |
Completed in 360 milliseconds