summaryrefslogtreecommitdiff
path: root/src/zenity.h
diff options
context:
space:
mode:
authorJeremy Bícha <jeremy.bicha@canonical.com>2023-08-10 14:14:35 -0400
committerJeremy Bícha <jeremy.bicha@canonical.com>2023-08-10 14:14:35 -0400
commitf8597587629cea96a21fcd058323799f44f3b3e5 (patch)
treef4d7cf09db438c8296b846e62c2cb623ddbf098d /src/zenity.h
parentRelease to unstable (diff)
parentNew upstream version 3.44.2 (diff)
downloadzenity-f8597587629cea96a21fcd058323799f44f3b3e5.tar.gz
zenity-f8597587629cea96a21fcd058323799f44f3b3e5.tar.bz2
zenity-f8597587629cea96a21fcd058323799f44f3b3e5.zip
Update upstream source from tag 'upstream/3.44.2'
Update to upstream version '3.44.2' with Debian dir 441cbc815fbb0ab86203cb218004e9d8ba6708f5
Diffstat (limited to 'src/zenity.h')
-rw-r--r--src/zenity.h9
1 files changed, 8 insertions, 1 deletions
diff --git a/src/zenity.h b/src/zenity.h
index 404eec77..c50a76bd 100644
--- a/src/zenity.h
+++ b/src/zenity.h
@@ -33,7 +33,14 @@ typedef enum {
ZENITY_ESC,
ZENITY_ERROR,
ZENITY_EXTRA,
- ZENITY_TIMEOUT
+ /* Previously, this was not specified to any value, which could cause it to
+ * clash with the custom response ID that happened to match it. We could set
+ * this to a negative value tha doesn't clash with one of GtkDialog's
+ * predefined response ID's as it's doubtful GTK will ever extend the GtkDialog
+ * API at this stage -- but technically negative values are reserved for the
+ * library and positive values for applications, according to gtkdialog.c
+ */
+ ZENITY_TIMEOUT = INT_MAX
} ZenityExitCode;
typedef struct {
bgstack15