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 (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 gone, theoretically, from the window when
this alert is called.)
Weird thing is that the exact same code in a different class works a-
ok, so I'm a little mystified, but knowing why an alert would just
beep, rather than come up, would be a great start. The previous
sheet is a progress metre, which comes up and goes away without any
user involvement. If I call the progress metre twice, there's
another beep and the panel is displayed detached from the window.
The "endpanel" function, which does get called, contains nothing
more than an orderOut:nil. Adding a close call neither helps nor
hinders.
So, what have I done to my window with this first sheet which causes
subsequent alerts to beep instead of displaying? Why does the
computer just beep and not give me an error message or some other
indication of what's wrong?
Thanks!
dale
_______________________________________________
Cocoa-dev mailing list ([email protected])
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
