From 182185e31e7dd4c8ff3f883e763fbe0bb8adfc70 Mon Sep 17 00:00:00 2001 From: Matthias Clasen Date: Fri, 11 Jul 2025 06:27:25 -0400 Subject: [PATCH] application: Clarify documentation Existing uses of before_emit in GTK will break if an app overrides before/after_emit without chaining up. Clarify in the documentation that these vfuncs need to chain up. --- gio/gapplication.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/gio/gapplication.c b/gio/gapplication.c index 38f1241b8..cbb69fefa 100644 --- a/gio/gapplication.c +++ b/gio/gapplication.c @@ -191,12 +191,12 @@ * alternative to handling some commandline options locally * @before_emit: invoked on the primary instance before 'activate', 'open', * 'command-line' or any action invocation, gets the 'platform data' from - * the calling instance + * the calling instance. Must chain up * @after_emit: invoked on the primary instance after 'activate', 'open', * 'command-line' or any action invocation, gets the 'platform data' from - * the calling instance + * the calling instance. Must chain up * @add_platform_data: invoked (locally) to add 'platform data' to be sent to - * the primary instance when activating, opening or invoking actions + * the primary instance when activating, opening or invoking actions. Must chain up * @quit_mainloop: Used to be invoked on the primary instance when the use * count of the application drops to zero (and after any inactivity * timeout, if requested). Not used anymore since 2.32