still having sheet problems
still having sheet problems
- Subject: still having sheet problems
- From: Ken Victor <email@hidden>
- Date: Mon, 9 May 2005 12:11:42 -0700
per comments from this list, i've given up even trying to use nested
sheets. instead, if there is an error on my sheet (which is on a
modal window), i then wish to display an app modal window. but i'm
still having some problems.
(in the below, the first modal window, has a table view, and cancel
and default buttons. clicking the default button displays the sheet.
the sheet has 2 secure text fields, a checkbox and a cancel button
and a default button. the default button is only enabled when both
secure text fields are non null. clicking the default button then
"validates" the contents of the 2 secure text fields; if they are not
valid, i wish to display a modal error alert.)
thus, given a modal window with a sheet as follows:
NSApp runModalForWindow:
NSApp beginSheet:
modalForWindow:
modalDelegate:
didEndSelector:
contextInfo:
i'm having some problems displaying an app modal error alert. if i
display the error alert via:
1) NSAlert runModal
2) NSAlert beginSheetModalForWindow: nil
modalDelegate:
didEndSelector:
contextInfo:
3) NSBeginCriticalAlertSheet(...) (with a nil docWindow parameter)
with method 1 i have the following problems:
a) the default button on my sheet stays blue (altho it
doesn't pulse) resulting in 2 "blue" buttons on the screen at the
same time
b) i can click in either the original modal window or the
sheet and the window (with its sheet) layer in front of the alert
dialog and the system beeps!
with method 2 (note passing of nil for first argument) i have the
following problems:
a) clicking anywhere in the alert dialog, including in the
default button, beeps; however, i can type enter or return and get
proper behavior.
b) if i click on the original modal window or the sheet and
the window (with its sheet) layer in front of the alert dialog and
the sheet appears as the key window. and while i can click the error
alert dialog to cause it to come to the front, it no longer takes
either mouse clicks or enter/return typing! and i'm forced to force
quit the app.
method 3 behaves the same as method 2.
i assume i must be doing something wrong! but i've spent hours on
this and haven't been able to figure out what i'm doing wrong. can
anyone suggest some things i should be looking at to try to fix this?
or indicate what further information i should supply so that this
list can help.
thanx much,
ken
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden