Closed GoogleCodeExporter closed 9 years ago
How hard is this to do on a scale of one to 42?
Original comment by chrisf.g...@gmail.com
on 15 Mar 2011 at 5:47
I'd say 15. The guts are already there in Growl; the skip hotkey would be
“close” and the “click” hotkey would be… well, “click”. We also
already have hotkey code in place.
Original comment by prhgr...@gmail.com
on 15 Mar 2011 at 11:42
Original comment by prhgr...@gmail.com
on 28 Mar 2011 at 9:31
If this works with MAS rules then we should look into it in 1.4.
Original comment by chrisf.g...@gmail.com
on 29 Jul 2011 at 6:24
Changing the owner on these to get them out of Peter's queue.
Original comment by chrisf.g...@gmail.com
on 15 Aug 2011 at 6:49
Original comment by ch...@growl.info
on 14 Nov 2011 at 12:43
Original comment by ch...@growl.info
on 28 Nov 2011 at 12:59
Original comment by ch...@growl.info
on 19 Jan 2012 at 10:45
I took a bit of time and implemented the simplest of these controls today,
pausing the display and its queue. Skipping would be easy enough, just stop
speaking the current item and start the next item in the queue.
Presently the new speech plugin dumps the rest of the note dictionary when it
starts speaking in a queue, so "click" feedback would require adding back in
the click context key at least.
Original comment by dan...@growl.info
on 23 Mar 2012 at 6:04
[e033a21e486b] for pause
[09a5b210651e] for skip/click feedback
Closing as fixed in source
Original comment by dan...@growl.info
on 24 Mar 2012 at 9:17
Growl 2 is released, marking these as fixed.
Original comment by ch...@growl.info
on 20 Sep 2012 at 3:16
Original comment by ch...@growl.info
on 11 Jan 2013 at 6:27
Original issue reported on code.google.com by
prhgr...@gmail.com
on 12 Jun 2010 at 9:27