A cleaner way to automatically call one method after another?

Question

Is it possible to design a method in such a fashion, that it knows it must automatically call a next method in succession upon exiting?

In the following example, I m

Answer 1

You could encapsulate the changes which would cause the form to refresh into form-level properties.

For instance,

private bool _showPriorityLine;
private bool ShowPriorityLine
{
    get { return _showPriorityLine; }
    set
    {
        _showPriorityLine = value;
        Refresh();
    }
}

Then your event would just be

private void PriorityLine_Click(object sender, EventArgs e)
{
    ShowPriorityLine = !ShowPriorityLine;
}

Of course, that only cleans up your code if you have several events manipulating the same variables that cause the form to need refreshing.

Answer 2

Don't call Refresh, call Invalidate. The mechanism you need is already built into Windows. Calling Invalidate simply makes a note that the window needs repainting. The operating system will eventually post a WM_PAINT message (typically after the root DispatchMessage call finishes, but the exact implementation is irrelevant).

Answer 3

Use a property that calls Refresh in the setter.

Answer 4

Sounds like what you want is Aspect Oriented Programming, there are a number of different frameworks to enable you to have stuff "magically" happen after some set of methods have run, have a look here AOP programming in .Net?

Answer 5

Something like this:

private void RefreshAfter(Action action)
    {
        action();
        Refresh();
    }

UPDATED TO MAKE IT MORE OBVIOUS:

    private void DoSomeUiShiznit(Action action)
    {
        action();
        // other parts of the code don't realize that Refresh has to be called.
        // But that's cool. I got it covered.
        Refresh();
    }

    private void PriorityLine_Click(object sender, EventArgs e)
    {
        DoSomeUiShiznit(() => { _showPriorityLine = !_showPriorityLine; });
    }

UPDATE -- Just a message to the down-voters:

What some of you are too blind to see is that this is not all that different from:

[SomeRefreshAttribute]  
private void PriorityLine_Click(object sender, EventArgs e)  
{
    _showPriorityLine = !_showPriorityLine;  
}  

Except that it is simpler, and doesn't require adding another framework to the solution. And yet the other answer suggesting as much don't get down-voted!

What's wrong with you people?

Answer 6

I'm not aware of any really clean way. One method would be to use PostSharp.