From 057f41532bd168e5b452a65900e8dfee19d5da4e Mon Sep 17 00:00:00 2001
From: Matthias Clasen <mclasen@redhat.com>
Date: Sun, 9 Feb 2020 10:55:37 -0500
Subject: [PATCH] Remove gtk_main_do_event from the docs

---
 docs/reference/gtk/gtk4-sections.txt |  1 -
 gtk/gtkmain.c                        | 38 ----------------------------
 2 files changed, 39 deletions(-)

diff --git a/docs/reference/gtk/gtk4-sections.txt b/docs/reference/gtk/gtk4-sections.txt
index 876c625b4b..7ce7f391dc 100644
--- a/docs/reference/gtk/gtk4-sections.txt
+++ b/docs/reference/gtk/gtk4-sections.txt
@@ -4424,7 +4424,6 @@ gtk_main_level
 gtk_main_quit
 gtk_main_iteration
 gtk_main_iteration_do
-gtk_main_do_event
 
 <SUBSECTION>
 gtk_grab_add
diff --git a/gtk/gtkmain.c b/gtk/gtkmain.c
index 0056c896a1..36ec67891d 100644
--- a/gtk/gtkmain.c
+++ b/gtk/gtkmain.c
@@ -1866,44 +1866,6 @@ handle_dnd_event (GdkEvent *event)
   return target;
 }
 
-/**
- * gtk_main_do_event:
- * @event: An event to process (normally passed by GDK)
- *
- * Processes a single GDK event.
- *
- * This is public only to allow filtering of events between GDK and GTK.
- * You will not usually need to call this function directly.
- *
- * While you should not call this function directly, you might want to
- * know how exactly events are handled. So here is what this function
- * does with the event:
- *
- * 1. Compress enter/leave notify events. If the event passed build an
- *    enter/leave pair together with the next event (peeked from GDK), both
- *    events are thrown away. This is to avoid a backlog of (de-)highlighting
- *    widgets crossed by the pointer.
- * 
- * 2. Find the widget which got the event. If the widget can’t be determined
- *    the event is thrown away unless it belongs to a INCR transaction.
- *
- * 3. Then the event is pushed onto a stack so you can query the currently
- *    handled event with gtk_get_current_event().
- * 
- * 4. The event is sent to a widget. If a grab is active all events for widgets
- *    that are not in the contained in the grab widget are sent to the latter
- *    with a few exceptions:
- *    - Deletion and destruction events are still sent to the event widget for
- *      obvious reasons.
- *    - Events which directly relate to the visual representation of the event
- *      widget.
- *    - Leave events are delivered to the event widget if there was an enter
- *      event delivered to it before without the paired leave event.
- *    - Drag events are not redirected because it is unclear what the semantics
- *      of that would be.
- * 
- * 5. After finishing the delivery the event is popped from the event stack.
- */
 void
 gtk_main_do_event (GdkEvent *event)
 {