search

brettpoole / growl

Automatically exported from code.google.com/p/growl
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

Speech display waits for previous message to complete causing a CPU drain #445

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Speech has a CPU drain in it. Growl sits there spinning, waiting for our 
previous message to be done speaking.

Original issue reported on code.google.com by ch...@growl.info on 10 Feb 2012 at 10:17

GoogleCodeExporter commented 8 years ago 
We do want to wait on it to finish speaking before starting the next, but we 
need to find a better way to do it than the current method.

Original comment by dan...@growl.info on 11 Feb 2012 at 12:10

GoogleCodeExporter commented 8 years ago 
addressed in [6ab1b8d6c0a9] internally to Growl, this however does not prevent 
Growl from talking over other applications on the system or waiting for other 
applications to finish speaking to start talking.  We have a date with the AX 
and Speech teams at WWDC to discuss.

Original comment by rarich...@gmail.com on 11 Feb 2012 at 4:53

GoogleCodeExporter commented 8 years ago

Original comment by ch...@growl.info on 11 Jan 2013 at 6:36