Yeah got the same problem right here but i don't think of it as a big deal he import somthing to help him in that class thought and i think that is what keep us away from understanding what he did
If it helps: objects have key: value pairs i.e. codyStats = {name: Cody, height: 60, eyes: blue}. Name is a key, and cody is the value. Classes are an abstraction of objects, or a blueprint for creating objects. The reasons this is done is for maintainability of large systems. We don't want Bill leaving off his eye color and adding in his favorite basketball team when billStats is created, so we use Classes. Classes make all the objects have the same keys. Everytime a new personStats is made we want them to have the same keys, otherwise we can't predict how each person will behave. That's the basics. Then we can add functions or methods to the class that we want all personStats to have. Latter on there will also be interfaces, mixins, etc that build on and address short comings of this system. It's completely normal not to get this concept the first time around. No one does. This sounds counter intuitive, but keep writing code that doesn't make 100% sense. One day, you'll have seen code like this a 100 times and when you watch a video explaining the method to the maddess it will all click.
This is pure gold!
Thanks you for everything
I did not understand the creation of another class "CameraType" inside a preexisting class Camera
Yeah got the same problem right here but i don't think of it as a big deal he import somthing to help him in that class thought and i think that is what keep us away from understanding what he did
its basicly an enum inside a class you can print the value with camera_type.value
god lesson
Sir you are great
The best
Can u pls explain me what was the purpose of enum and what r enums
I like your other videos but I think I'm particularly slow to pick up the class/object thing. So this video lost me pretty quickly.
If it helps:
objects have key: value pairs i.e. codyStats = {name: Cody, height: 60, eyes: blue}. Name is a key, and cody is the value.
Classes are an abstraction of objects, or a blueprint for creating objects. The reasons this is done is for maintainability of large systems. We don't want Bill leaving off his eye color and adding in his favorite basketball team when billStats is created, so we use Classes. Classes make all the objects have the same keys. Everytime a new personStats is made we want them to have the same keys, otherwise we can't predict how each person will behave.
That's the basics. Then we can add functions or methods to the class that we want all personStats to have. Latter on there will also be interfaces, mixins, etc that build on and address short comings of this system.
It's completely normal not to get this concept the first time around. No one does. This sounds counter intuitive, but keep writing code that doesn't make 100% sense. One day, you'll have seen code like this a 100 times and when you watch a video explaining the method to the maddess it will all click.
everything was good until the self.position.log()