The main problem with that is that you’re going to generate garbage (it will allocate a new array each time you use it) and you’ll see a lot of boxing/unboxing costs from casting an enumeration to object and back (you can read more on that here: http://msdn.microsoft.com/en-us/library/yz2be5wk.aspx).

True that your method doesn’t require the static initialization stuff and is a bit simpler, but I personally feel the performance implications aren’t worth it.

public static bool AreAnyButtonsPressed(this GamePadState state, params object[] buttons)
{
foreach (Buttons button in buttons)
{
if (state.IsButtonDown(button))
return true;
}
return false;
}

You can redefine this as a for loop with an “is” check for object -> Buttons if you’re concerned about the whole foreach garbage thing.

(I don’t know how to format code blocks on this site, just registered.)

- Menus should accept A & Start to activate an item
- Menus should accept B & Back to go back
- Sometimes you want multiple buttons mapped to the same action in a game

I don’t personally see it as overkill because it lets me write the code I want to write when handling input. Plus this is actually just a part of my larger set of GamePadState extension methods, so it’s not the only thing I have in there.