diff options
author | Jon Trowbridge <trow@ximian.com> | 2001-04-20 16:15:24 +0800 |
---|---|---|
committer | Jon Trowbridge <trow@src.gnome.org> | 2001-04-20 16:15:24 +0800 |
commit | 7221bd79c2c61f5c66f35ffcf0f471f85bdb6ac7 (patch) | |
tree | 5f890cfefd04a8ec0c32aabdaebdf83801164876 /doc/es/usage-notes.sgml | |
parent | 4ab57773ab02e3460e8b34897662fe4eb66c7ad7 (diff) | |
download | gsoc2013-evolution-7221bd79c2c61f5c66f35ffcf0f471f85bdb6ac7.tar.gz gsoc2013-evolution-7221bd79c2c61f5c66f35ffcf0f471f85bdb6ac7.tar.zst gsoc2013-evolution-7221bd79c2c61f5c66f35ffcf0f471f85bdb6ac7.zip |
Limit total matches, for better performance on slow machines. It is
2001-04-20 Jon Trowbridge <trow@ximian.com>
* gal/e-text/e-completion-test.c: Limit total matches, for better
performance on slow machines. It is supposed to be a test, so
correctness of the completion operations isn't really a
priority...
* gal/e-text/e-completion-view.c (e_completion_view_construct):
Set GTK_CAN_FOCUS flag.
* gal/e-text/e-entry.c (e_entry_show_popup): Evil! Evil! Unclean!
Unclean! Manually check if the pointer is in the area where the
popup is going to appear, and if it is, warp the pointer out of
the way. After days of fucking around, this horrible hack is the
only way that I've been able to figure out to keep the focus from
being taken away from the entry and ending up somewhere strange
when the popup pops up. (The main problem is with the case of
focus-follows-cursor --- click-to-focus works fine. Sawfish
idiocincracies may also be causing problems, but I don't want to
unjustly accuse the WM of anything, as tempting and appealing as
that can be.)
(key_press_cb): Proxy for forwarding the popup's key press events
to the entry.
(key_release_cb): Proxy for forwarding the popup's key release
events to the entry.
These proxies should be enough to take care of my focus problems.
Unfortunately, they aren't, and the pointer-warping-focus-horror
is required for reasons that I don't fully understand.
* gal/e-text/e-text.c (_get_xy_from_position): Made
_get_xy_from_position return a boolean. It returns TRUE if the
computation was successful
(and if valid data is now in *xp and *yp), FALSE otherwise. Make
sure that text->lines is not NULL, and return FALSE if it is.
(_get_position): Test that _get_xy_from_position returns TRUE
before using the values in x and y.
(_get_position): Test that _get_xy_from_position returns TRUE
before using the values in x and y.
Garbage values being returned in passed-in pointers created a race
condition where you could hang an EText if you deleted the entire
contents of the buffer really quickly.
svn path=/trunk/; revision=9468
Diffstat (limited to 'doc/es/usage-notes.sgml')
0 files changed, 0 insertions, 0 deletions