Re: how to determine the next control in validating event
From: Bruce Wood (brucewood_at_canada.com)
Date: 01/25/05
- Next message: ALI-R: "Re: Boxing and Unboxing of Value-Types when passed to a method call"
- Previous message: Bruce Wood: "Re: Boxing and Unboxing of Value-Types when passed to a method call"
- In reply to: Alex Bink: "how to determine the next control in validating event"
- Next in thread: Alex Bink: "Re: how to determine the next control in validating event"
- Reply: Alex Bink: "Re: how to determine the next control in validating event"
- Messages sorted by: [ date ] [ thread ]
Date: 24 Jan 2005 17:01:57 -0800
You want to set CausesValidation on that other, specific control to
false. This will allow that control to gain focus without firing the
Validating event on the text box that the user is leaving. Sort of.
You can read about all the gory details of CausesValidation and
validating in this thread:
(watch for line wrap on the URL)
The bottom line is that CausesValidation will (with a few caveats)
solve your problem by preventing your Validating event handler from
being called (sort of... like I said, read the other link), so you
don't have to test for which control has focus in your Validating event
handler.
- Next message: ALI-R: "Re: Boxing and Unboxing of Value-Types when passed to a method call"
- Previous message: Bruce Wood: "Re: Boxing and Unboxing of Value-Types when passed to a method call"
- In reply to: Alex Bink: "how to determine the next control in validating event"
- Next in thread: Alex Bink: "Re: how to determine the next control in validating event"
- Reply: Alex Bink: "Re: how to determine the next control in validating event"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|