After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 319657 - Orca should speak 'find' command new line.
Orca should speak 'find' command new line.
Status: RESOLVED FIXED
Product: orca
Classification: Applications
Component: speech
unspecified
Other All
: Normal enhancement
: 2.18.0
Assigned To: Rich Burridge
Orca Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-10-24 20:56 UTC by Rich Burridge
Modified: 2008-07-22 19:24 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Patch to implement the enhancement. (5.62 KB, patch)
2006-10-09 18:43 UTC, Rich Burridge 		none Details | Review

Description Rich Burridge 2005-10-24 20:56:51 UTC 
When in a text editor such as GEdit, orca should speak the new
line landed on when doing a 'find' command.
Comment 1 Rich Burridge 2006-05-15 18:18:00 UTC 
This is definitely something we could do in the gedit script.
Comment 2 Rich Burridge 2006-10-06 21:43:00 UTC 
Note that the workaround for this currently is to Alt-Tab back to the
main gedit window after the Find operation, and do a Where-ami-i with
Numpad-Enter.
Comment 3 Rich Burridge 2006-10-09 18:43:07 UTC 
Created attachment 74368 [details] [review]
Patch to implement the enhancement.

See the comments in the gedit.py script for more details.

Couple of caveats:

1/ If the find phrase is not found, then "Phrase not found" is spoken 
   twice because we apparently get two identical
   "object:property-change:accessible-name" events.
2/ Nothing is done here for Control-G (Find Next) or Shift-Control-G
   (Find Previous). If you need that functionality, then it can also
   done via the Find dialog, which now speaks it nicely.
Comment 4 Rich Burridge 2006-10-09 18:44:20 UTC 
Changes checked into CVS HEAD. Closing as FIXED.