12 Replies
For starters, what are you trying to do?
Because you could just check
Keyboard.GetState().IsKeyDown(...) instead of trying to make a bunch of propertiesbut what if i want proprerties ?
Then deal with the mess
at least capitalize them, and use the
=> expression syntax
Why do you want properties?
to turn this into this
But why :pwetty:
Seems like lots of extra work for very little payoff
i had enouth of copy+past
i will allways keep it when i code
don't forget other snippets included: multiple functions to change console colors (aka
Console.SetRed() / Blue / Green / etc), get all processes in OS (aka Processes.Google / notepad / vscode / etc).
it is super useless
at least you can create extension method to avoid this boilerplate code
or write custom SG
Shorter, but no boilerplate