ppapi_simple

native_client_sdk/src/libraries/ppapi_simple/ppapi_event.cc

+/* Copyright (c) 2013 The Chromium Authors. All rights reserved.
+ * Use of this source code is governed by a BSD-style license that can be
+ * found in the LICENSE file.
+ */
+
+#include "ppapi/c/pp_instance.h"
+#include "ppapi/c/pp_module.h"
+
+#include "ppapi_simple/ppapi_event.h"
+#include "ppapi_simple/ppapi_simple_instance.h"
+#include "ppapi_simple/ppapi_simple_main.h"
+
+
+void PSPostEvent(PSEventType type) {
+  PSInstance::GetInstance()->PostEvent(type);
+}
+
+void PSPostBoolEvent(PSEventType type, PP_Bool state) {
+  PSInstance::GetInstance()->PostEvent(type, state);
+}
+
+void PSPostVarEvent(PSEventType type, struct PP_Var var) {
+  PSInstance::GetInstance()->PostEvent(type, var);
+}
+
+void PSPostResourceEvent(PSEventType type, PP_Resource resource) {
+  PSInstance::GetInstance()->PostEvent(type, resource);
+}
+
+PSEvent* PSTryToAcquireEvent() {
+  return PSInstance::GetInstance()->TryAcquireEvent();
+}
+
+PSEvent* PSWaitForAcquireEvent() {

[Sam Clegg, 2013/05/29 04:48:25]

How about naming these just 
   PSEventPoll()
and
   PSEventWait()

I've always found this naming convention used by SDL to be
very obvious:

http://www.libsdl.org/intro.en/usingevents.html

Also, what do you think about starting all functions in this file with the
common PSEvent prefix (I like C modules where everything starts with a common
prefix, but I'm not sure the
style guide says anything about this).

[noelallen_use_chromium, 2013/05/30 00:25:07]

Done.

+  return PSInstance::GetInstance()->WaitAcquireEvent();
+}
+
+void PSReleaseEvent(PSEvent* event) {
+  PSInstance::GetInstance()->ReleaseEvent(event);
+}
+
+void PSSetEventFilter(uint32_t filter) {
+  PSInstance::GetInstance()->SetEnabledEvents(filter);
+}
+