diff options
author | rjkroege@google.com <rjkroege@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-10-21 20:30:30 +0000 |
---|---|---|
committer | rjkroege@google.com <rjkroege@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-10-21 20:30:30 +0000 |
commit | 9317bdedaac5718c5499efe081df23c2d6903d80 (patch) | |
tree | 77dd995183ed17ac9303a44bebefee9c4ad20374 /base/message_pump_glib.h | |
parent | 66980d85fefe26261b310f35375a31bb91abd0c3 (diff) | |
download | chromium_src-9317bdedaac5718c5499efe081df23c2d6903d80.zip chromium_src-9317bdedaac5718c5499efe081df23c2d6903d80.tar.gz chromium_src-9317bdedaac5718c5499efe081df23c2d6903d80.tar.bz2 |
Revert 63397 - Add a message pump for touchui=1
The message pump reads events directly from X. For most events, it passes them
on to GDK for normal processing. It consumes some events (e.g. keypress events)
to demonstrate how it's intended to work. This, of course, makes chrome mostly
unusable since you can only use the mouse to do things. But this is a small
first step towards capturing events through MPX (e.g. touch etc.) and processing
them as chrome pleases.
glib message pump: Slightly change architecture
This changeset breaks down the glib message pump a little so that it can be
easily subclassed. The next set of commits will introduce a subclass that still
uses GTK and GDK widgets, but reads events directly from X instead of through
GTK/GDK.
Review URL: http://codereview.chromium.org/3748002
Patch from Sadrul Chowdhury <sadrul@chromium.org>.
TBR=rjkroege@google.com
Probably a dynamic link problem with -lX11.
Review URL: http://codereview.chromium.org/4007004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@63403 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'base/message_pump_glib.h')
-rw-r--r-- | base/message_pump_glib.h | 9 |
1 files changed, 0 insertions, 9 deletions
diff --git a/base/message_pump_glib.h b/base/message_pump_glib.h index 31d37c0..f6d022a 100644 --- a/base/message_pump_glib.h +++ b/base/message_pump_glib.h @@ -57,11 +57,6 @@ class MessagePumpForUI : public MessagePump { // Like MessagePump::Run, but GdkEvent objects are routed through dispatcher. virtual void RunWithDispatcher(Delegate* delegate, Dispatcher* dispatcher); - // Run a single iteration of the mainloop. A return value of true indicates - // that an event was handled. |block| indicates if it should wait if no event - // is ready for processing. - virtual bool RunOnce(GMainContext* context, bool block); - virtual void Run(Delegate* delegate) { RunWithDispatcher(delegate, NULL); } virtual void Quit(); virtual void ScheduleWork(); @@ -84,10 +79,6 @@ class MessagePumpForUI : public MessagePump { // receiving a notification callback. void RemoveObserver(Observer* observer); - // Dispatch an available GdkEvent. Essentially this allows a subclass to do - // some task before/after calling the default handler (EventDispatcher). - virtual void DispatchEvents(GdkEvent* event); - private: // We may make recursive calls to Run, so we save state that needs to be // separate between them in this structure type. |