When I was a kid. I started out in the building trade, clueless, and I worked as a trainee plasterer for a while. My boss told me he wanted one side of the room skimmed.
So on my first day, haven never plastered in my life, do you think I said yes sure, I will do that right away?
Or do you think I said, but sir, how do I go about making the mix to plaster the wall?
Obviously, you need to learn to mix the bond, before you even mix the plaster. But I didn't know that, until I asked the question; how do I get started?
Until It was explained to me, I eventually learned, and I learned by asking the same questions I already kinda knew the answers too, because he trained me like that. He told me, if you don't know something or if you're in doubt, ask me what to do.
My point is... You've just been given a book on how Windows works. Herein is the point...had you read about any of the available API's in the book, possible mentioned events or even the chapters on Windows itself, you would have a general consensus to understanding the events you are working with. Well enough for you to come back and ask a question relative to what you're trying to do.
Writing code is easy. Doing it right is not so easy. Knowing the mechanics of what makes you write properly written code that actually works clearly depends upon how well you have been thought or how well you teach yourself. And In your case; you came here for help and guidance, but insistingly outlined your desire to not be educated or to be directed to any documentation.
You don't learn to bond and plaster a wall without learning how to mix the substance. The same applies to programming. You won't become any good at it with an attitude like yours. Becoming a programmer requires patients and lots of reading.