--
Have a great day,
Alex
mehg...@gmail.com
On Feb 6, 2014, at 7:39 PM, Andrew Thompson wrote:
> If you post to the speech-dev list you'll likely get a more detailed reply as
> Apple's TTS engineers hang out there.
Thank you, I didn't know that list even existed! That will indeed be a gre
In my app I have a floorplan (an image) drawn in a UIScrollView. There are
annotations on the floorplan that are drawn in a UIView that overlays the
scroll view. I do this because I don't want the annotations to change size as
the user zooms the scroll view, only position.
I have a tap gesture
If you post to the speech-dev list you'll likely get a more detailed reply as
Apple's TTS engineers hang out there.
I believe it is possible to hook up the synthesizer as an Audio Unit and
capture the output that way.
A more basic approach would be to use the venerable UNIX mkfifo function to
Hello again,
The NSSpeechSynthesizer can output speech to a sound output device or a file.
However, I want to capture the output and store it as audio data, so I can
string together multiple outputs and then save the whole thing to a file. I've
looked, but the only link I found that might have o
Hello everyone,
In looking at the class reference for the NSSpeechRecognizer, you are told that:
Through an NSSpeechRecognizer instance, Cocoa applications can use the speech
recognition engine built into OS X to recognize spoken commands. With speech
recognition, users can accomplish complex, mu
On Feb 6, 2014, at 12:51 PM, Jens Alfke wrote:
> But it would be more straightforward to create a new NSException object with
> the same attributes as the one you caught but with your own info added to its
> userInfo.
On Feb 6, 2014, at 1:05 PM, Uli Kusterer wrote:
> What NSError does in this
On 06 Feb 2014, at 19:44, Carl Hoefs wrote:
> I would like to be able to add additional context info to certain exceptions
> that the system might generate. Since NSException's userInfo dict is nil in
> such cases it would be convenient to add an error context dict to the
> exception and then
On Feb 6, 2014, at 11:08 AM, Carl Hoefs wrote:
> If I add a "@throw e;" in the @catch block, would that have the effect of
> "tagging" the unhandled exceptions with my info context, assuming I could add
> my own userInfo to it?
If you could mutate the object e, then re-throw it, yes. You're t
I don't see any such behavior in the Objective-C language reference. Feel free
to read those chapters for more information. :) There's also an Apple document
"Introduction to Exception Programming Topics for Cocoa" which has some good
information.
Doug Hill
On Feb 6, 2014, at 11:08 AM, Carl Ho
Doug,
If I add a "@throw e;" in the @catch block, would that have the effect of
"tagging" the unhandled exceptions with my info context, assuming I could add
my own userInfo to it?
-Carl
On Feb 6, 2014, at 11:57 AM, Doug Hill wrote:
> Carl,
>
> In your case below, I don't see the value of a
Carl,
In your case below, I don't see the value of adding any info to the exception
as it's just been caught and won't be seen by anyone else. Since your exception
handler knows about this special error condition, if you want to propagate this
exception, just create a new exception object of yo
I would like to be able to add additional context info to certain exceptions
that the system might generate. Since NSException's userInfo dict is nil in
such cases it would be convenient to add an error context dict to the exception
and then handle/display it.
@try {
...;
}
@catch (NS
On Jan 30, 2014, at 2:14 PM, Jens Alfke wrote: > And C++
partisans would tell you that many of these things are limitations of the usual
C++ runtimes, not the language itself, but I'm not aware of any current
runtimes that avoid them. I bet those same partisans would be the first to the
barric
13 matches
Mail list logo
