On May 28, 2008, at 12:37 PM, Sherm Pendley wrote:
I strongly suspected that at first, but you said your callback method
*was* being called - and it's called by the framework in response to
your own call to -endSheet:returnCode:. So now I'm confused. Were you
calling the callback method directly
On Wed, May 28, 2008 at 1:19 PM, Dale Jensen <[EMAIL PROTECTED]> wrote:
>
> I was neglecting to call [NSApp endSheet:theSheet returnCode: 0];
I strongly suspected that at first, but you said your callback method
*was* being called - and it's called by the framework in response to
your own call to
Thanks to Jim Matthews, a solution for the archive:
I was neglecting to call [NSApp endSheet:theSheet returnCode: 0];
It would still be nice to hear from someone at Apple as regards the
beeping, but this solves it for me.
Thanks, Jim!
dale
--
Dale Jensen
Ntractive, LLC
[EMAIL PROTECTED]
h
Try linking with debug versions of the frameworks, these often
print info to the console on the nature of an error that may
otherwise just beep.
Kevin G.
(Nary a response from last post, I'll try again.)
I've got a situation where an alert, attached as a sheet, just beeps
when it's called (
(Nary a response from last post, I'll try again.)
I've got a situation where an alert, attached as a sheet, just beeps
when it's called (instead of displaying and interacting with the
user.) I'm about 99.99% certain that this is being caused by a sheet
that comes up prior to the alert (not
I've got a situation where an alert, attached as a sheet, just beeps
when it's called (instead of displaying and interacting with the
user.) I'm about 99.99% certain that this is being caused by a sheet
that comes up prior to the alert (not at the same time -- the previous
sheet is long go
