[Nautilus-list] [PATCH] "event-after" portion of location_bar
- From: David Emory Watson <dwatson cs ucr edu>
- To: Darin Adler <darin bentspoon com>
- Cc: Nautilus <nautilus-list lists eazel com>, Alex Larsson <alexl redhat com>
- Subject: [Nautilus-list] [PATCH] "event-after" portion of location_bar
- Date: Mon, 25 Feb 2002 18:21:23 -0800
On Mon, 2002-02-25 at 08:32, Darin Adler wrote:
> Owen suggested changing this to use two signal handlers:
> http://lists.gnome.org/archives/gtk-app-devel-list/2002-January/msg00243.htm
> l
>
> - connect_after to catch return_value = FALSE returns
In the current code the "return_value == FALSE" case implies that we
skip auto-completion.
> - connect to ::event-after to catch all key presses afterwards
If the auto-completion code resides primarily in the event-after
callback then the "return_value == FALSE" case will not exist (i.e. it
will not have any effect, you can't skip something your not doing)...
If there are specific events that we want avoid handling then we will
need to a) put code in the event-after callback to recognize these
events or b) somehow stop the event-after callback from occurring in the
"return_value == FALSE" case. Are you sue this needs to be done?
Since I am still unclear on exactly what the "return_value == FALSE" is
comprised of (I've only seen it occur with things like, for ex.,
Gdk_Shift and this case is properly handled by the
entry_would_have_inserted_characters () function), the attached patch
only connects to event-after.
On the bright side, this patch appears to Work Perfectly (tm).
----
OK, here's where I go hide for fear of being completely wrong...
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]