222887 - Problems/incompatibilities with MacSpeech iListen voice recognition software

Status: RESOLVED EXPIRED

(SeaMonkey :: General, defect)

Description

[Chris Andrichak]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.5) Gecko/20031007
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.5) Gecko/20031007

MacSpeech iListen is voice recognition software for the Macintosh. In general it
works OK with Mozilla, but there are a couple problems that have existed for a
long time:
- iListen has a "choose menu" scripting command to choose a menu command that
will not work with a Mozilla menu unless you manually pull down the menu first.
After you have used the menu once, the "choose menu" scripting command will then
function properly. This scripting command works properly with pretty much every
other OSX application.
- when you are dictating text, you can use the correction facility of  iListen
to correct what you have just dictated. If you use correction while you are
composing a new e-mail message (the body text), the message will hang up when
you try and send it at the "assembling message" stage. You must then quit that
message send and attempt Resending a message later.

These problems exist with iListen 1.6.1, Mac OSX 10.2.6

I realize that these sound like problems in iListen, but especially the menu
problem is something that only appears with in this particular program
(actually, also AOL for Mac OSX which is built from the same code base), so I
believe there is some sort of interaction at least or something different about
Mozilla.

I and copying the iListen developers on this bug to hopefully produce some fixes.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1

[Chris Andrichak]

[e-mail]
is the support email

Comment 2

[Chris Andrichak]

problems with the correction function cooperating between iListen and mozilla
seem to have been fixed with the release of iListen 1.6.4.

I am seeing promising results with the menu problems since the release of
mozilla 1.7b. Still testing this.

Comment 3

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 4

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.

Comment 5

[Chris Andrichak]

The problems described in this bug have basically been corrected, so resolve/fixed is okay.