Question

I have an InfoPath form which I need to conditionally disable it’s OnChange events. Since it’s not possible to bind the event handlers after the form has loaded, I’m forced to rely on a global counter which indicates whether an OnChange event should be executed.
Inside each OnChange event, I check whether SuppressEventsCount == 0 before performing any actions.
To suppress events during the execution of some function or another, I simply set SuppressEventsCount++, and — again when the function exits. The biggest problem with doing this is that it’s not exception safe. So I had the bright idea to wrap the SuppressEvents counter in a class which implements iDisposable

using(SuppressEvents s = new SuppressEvents()){
   // OnChange events fired here are ignored
} // OnChange events enabled again

This is working, but it’s still not as ideal as a c++ solution which doesn’t require the use of the “using” directive at all.

Is there some way to either:

1. Trigger a destructor or some function the moment an object goes out of scope, OR
2. Prevent the SuppressEvents object from being initialised outside of a “using” directive entirely

Answer 1

In relation to question 2, it might be possible to get around it by providing a different interface to consumers of the code. Instead of providing a public class that implements IDisposable, and hoping they wrap it in a using, you could provide a static method that takes a function to execute in a “suppressed” context:

public static class EventSuppressor {
    public void Suppress(Action action) {
        using (var s = new SuppressActions()) {
            action();
        }
    }

    private class SuppressActions : IDisposable {
        ...
    }
}

Then consumers can use this as follows:

EventSuppressor.Suppress(() => {
    // OnChange events fired here are ignored
}) // OnChange events enabled again

Of course, you have to work out whether this design is appropriate, as this will result in extra function calls, compiler generated classes and closures etc.