I've recently completed OOP in python, after a dreadful amount of time, effort, sweat and dedication learning OOP, testing different codes and practicing your own ones - hours of taking notes until I've reached a point where I'm confident enough to say I understand and know how to write in OOP.
After intense learning, I thought I was good enough to do whatever is gonna be thrown at me, or perhaps even exceed the expectations needed to do pygame. So I gave pygame, my first library a try.
And boy I was wrong, I was struggling like hell, it was not because I did not understand the code - it was because the poor explanation given by nearly every tutorial. The explanations were very vague and each tutorial does it differently to others, some contradicting to each other's point. The whole thing is a mess! All the explanation given, including the documentation itself is rather too vague for anyone to learn.
I've spent 4-5 days learning pygame and I'm still on the basic, trying to make my own test and filling in the holes that the tutorial did not explain. To name a few:
When you create a display as follows "pygame.display.set_mode((500,200))", a window appeared - but I was not able to close it, and the moment I try to - it became unresponsive. And tell you what, I've only seen ONE tutorial that has mentioned the above experience - it caused me to think that there was an installation problem and I spent hours researching on the wrong thing only to discover about event queues later
The event queue are poorly explain, the concept was poorly explained and they did not even define what is exactly meant by "event". A proper tutorial would first mention that events queues are a list containing all types of interaction on the display, including hovering the mouse or clicking on it. NOT EVEN A SINGLE TUTORIAL MENTIONED THIS, I HAD TO DEDUCT THIS MYSELF AFTER HOURS OF TESTING. I'm surprised this was not mentioned considering how important it is to know it's a list, this is what you need the user to know to be able to manipulate the events later on.
The second one just stagnates everything, without knowing what the hell an event queue actually is - how would one be able to even understand the methods "event.get()" and "event.poll()". I had to deduce all these missing holes myself starting from nowhere and asking help outside.
The vagueness of these tutorial is what caused me to have progressed so slowly. The documentation did not help at all and it only mentions what the function does and what the argument does, does not tell us what type of data is being returned or where specifically the action is taking place.
My most recent struggle was trying to make sense out of this: "pygame.event.poll()¶ get a single event from the queue poll() -> EventType instance Returns a single event from the queue. If the event queue is empty an event of type pygame.NOEVENT will be returned immediately. The returned event is removed from the queue."
It did not specify WHICH EVENT is being taken from the queue - I first interpreted it to be taking the event at the end of the queue where that line of code is executed - because that's what all the tutorial seems to be pointing at. After hours of aimless testing was I able to discover that the poll() method is actually taking queues at the start of the queue for each iteration.
Please mods, do something about it - I tried to define my struggle as best as I can. I cannot be simply like others who follows the tutorial writing the exact same code, thinking they know much when they actually don't. I'm a kinetic learner and cannot simply aimless follow, if I have a spot of knowledge missing in my head - I would immediately stop following and try to find other sources which doesn't seem to have much effect.
Much Appreciation