L
Laura Stern
Guest
#2 - Mike Fechner answered this already: Use the Validating event and set e:Cancel to TRUE (where e is the eventArgs parameter to the event handler). I remember having the same Cancel button problem years ago when I first did GUI programming. I can't remember what I did to handle that. I think there should be a property on the Cancel button. For example, try setting the CausesValidation property to false. #3 - The window does not write data. The window does nothing automatically. If you just have a bunch of text boxes, for example, it is up to your code to do something with the values. You could have an event handler for the OK button which will do whatever work you need to do. Mike was talking about a Validate event, not a Validate method. But I think just subscribing to the Click event of the OK button would work. If you are using data binding, that is a different story. With data binding, updates that are made through a control will either be automatically propagated back to the data source (depending on the BindingSource settings), or it will use an event mechanism so that your code can make changes at the time of the user change. If you don't know what I mean by data binding, then you don't need to worry about it right now! #4 - When an event handler runs, the first argument will always be the instance of the control that is sending the event. You can always get its Type (obj:GetType()), and then access the Name (or FullName) property from that. #5 - Yup. That is a .NET thing. You cannot call Application:Run() a 2nd time after you have been kicked out of it. Sorry.
Continue reading...
Continue reading...