summaryrefslogtreecommitdiff
path: root/gtk/gtksearchbar.c
diff options
context:
space:
mode:
authorBastien Nocera <hadess@hadess.net>2013-06-03 15:07:07 +0200
committerBastien Nocera <hadess@hadess.net>2013-06-14 19:10:39 +0200
commit3d11b9b758a74f9960a402aea2c6fcb5cb8b5220 (patch)
treef491466909238228f18a0c67db8815be7078ae13 /gtk/gtksearchbar.c
parent19c5b37d9de6912b98e7c75b3a4bc58d600b0da1 (diff)
downloadgtk+-3d11b9b758a74f9960a402aea2c6fcb5cb8b5220.tar.gz
GtkSearchBar: Mention we don't handle Ctrl+F for the app
There's probably an expectation from the app developers that Ctrl+F or similar common shortcuts for starting a search will be handled by the widget, when this is not the case. Explicitely mention it in the docs to avoid confusion. https://bugzilla.gnome.org/show_bug.cgi?id=701523
Diffstat (limited to 'gtk/gtksearchbar.c')
-rw-r--r--gtk/gtksearchbar.c3
1 files changed, 2 insertions, 1 deletions
diff --git a/gtk/gtksearchbar.c b/gtk/gtksearchbar.c
index db0c5545d3..c45b3c54cc 100644
--- a/gtk/gtksearchbar.c
+++ b/gtk/gtksearchbar.c
@@ -47,7 +47,8 @@
*
* For keyboard presses to start a search, events will need to be forwarded
* from the top-level window that contains the search bar. See
- * gtk_search_bar_handle_event() for example code.
+ * gtk_search_bar_handle_event() for example code. Common shortcuts such as Ctrl+F
+ * should be handled as an application action, or through the menu items.
*
* You will also need to tell the search bar about which entry you are
* using as your search entry using gtk_search_bar_connect_entry().