As I thought this over, while on a long walk, apply might not be the
place. That is, if pressing OK gets you to apply and the code discovers
how do you get back to the dialog. I think you may have answered that
below with the validation code.
Alan Gauld wrote:
"Wayne
Watson"
wrote
Yes,
"Wayne Watson" wrote
Yes, apply is invoked when I click OK. apply has one statement,
and returns to the caller, which then checks the validity
(try-except)
of values passed back to it. It seems like apply should do all the
try-except work instead.
Yes, I'd agree that is how it should work.
Yes, apply is invoked when I click OK. apply has one statement, and
returns to the caller, which then checks the validity (try-except) of
values passed back to it. It seems like apply should do all the
try-except work instead. The code spends quite a few lines setting
things up to pass back. I'
"Wayne Watson" wrote
The program I'm modifying uses something of a primitive way
to check the validity of values entered into widgets on a larger
dialog.
You can bind events to the individual entry widgets to check values
when you navigate away from the widget. Or even on each keypress...
.
Title: Signature.html
The program I'm modifying uses something of a primitive way to check
the validity of values entered into widgets on a larger dialog. It uses
try-except after the user has pressed OK and departed from the dialog.
Isn't this supposed to be done in the apply method for the di
