How do I force the NSNumberFormatter for my NSTextField to execute?
I have a sheet which contains, among other things, an NSTextField with an attached standard NSNumberFormatter and an OK button which closes the sheet and processes all the user inputs. I have a
control:didFailToFormatString:errorDescription delegate routine which handles incorrect entries. It puts up an alert panel, then replaces the user's bad entry with the contents before editing began.
If the user enters something which doesn't obey the specified format and range, everything works fine as long as the user signals completion of editing the field by typing "enter", "return" or "tab". The delegate routine gets control, the alert panel comes up, and the bad data gets replaced.
But if the user clicks on the OK button to end the entire sheet with an invalid update to the NSTextField in progress, my delegate routine never gets control. Instead, the bad contents get replaced with a zero and the sheet closes. Zero, although a legal value, is rarely desirable. The user may not realize that he/she made an invalid entry because the sheet closes with no error indication.
In my action routine which responds to OK, I want to force error checking on the NSTextField programmatically, and (if an error is found) abort the completion of the sheet. I cannot figure out how to do this without essentially recoding what the NSNumberFormatter is supposed to do.
I have tried directly calling the action routine for the NSTextField. I have tried using NSApplication's sendAction:to:from routine to initiate the action through the usual channels. I have tried simply using validateEditing on the NSTextField. I have even tried sending makeFirstResponder:nil to the window, hoping that forcing the text field to give up responder status would initiate the error checking. None of these things have any effect at all. The error checking in my code does not take place. But obviously the formatter is getting involved somehow, because the invalid entry turns magically into a 0.
In desperation, I have tried calling the formatter directly
(getObjectValue:forString:errorDescription). I have also tried calling the
control:didFailToFormatString:errorDescription delegate routine directly. These last two attempts resulted in strange and undesirable behavior of the program, but no alert panel appeared.
I am out of ideas. Can anyone suggest anything?
control:didFailToFormatString:errorDescription delegate routine which handles incorrect entries. It puts up an alert panel, then replaces the user's bad entry with the contents before editing began.
If the user enters something which doesn't obey the specified format and range, everything works fine as long as the user signals completion of editing the field by typing "enter", "return" or "tab". The delegate routine gets control, the alert panel comes up, and the bad data gets replaced.
But if the user clicks on the OK button to end the entire sheet with an invalid update to the NSTextField in progress, my delegate routine never gets control. Instead, the bad contents get replaced with a zero and the sheet closes. Zero, although a legal value, is rarely desirable. The user may not realize that he/she made an invalid entry because the sheet closes with no error indication.
In my action routine which responds to OK, I want to force error checking on the NSTextField programmatically, and (if an error is found) abort the completion of the sheet. I cannot figure out how to do this without essentially recoding what the NSNumberFormatter is supposed to do.
I have tried directly calling the action routine for the NSTextField. I have tried using NSApplication's sendAction:to:from routine to initiate the action through the usual channels. I have tried simply using validateEditing on the NSTextField. I have even tried sending makeFirstResponder:nil to the window, hoping that forcing the text field to give up responder status would initiate the error checking. None of these things have any effect at all. The error checking in my code does not take place. But obviously the formatter is getting involved somehow, because the invalid entry turns magically into a 0.
In desperation, I have tried calling the formatter directly
(getObjectValue:forString:errorDescription). I have also tried calling the
control:didFailToFormatString:errorDescription delegate routine directly. These last two attempts resulted in strange and undesirable behavior of the program, but no alert panel appeared.
I am out of ideas. Can anyone suggest anything?
G5 dual 2.0 GHz, Mac OS X (10.3.9)
