Please take into account that you are studying a e book explaining a strategy to make a sport, in SFML. You’ll doubtless find yourself having a working sport, however not one which is able to ship.
To make it easier so that you can “get one thing working”, they hard-coded the values as a substitute of getting you write an entire system to load a stage from information.
That is advantageous, although. This type of e book is usually step one in getting you going. When you’re completed with it, you will then must increase and “repair all the issues you see with it”: adapt it for a number of display sizes, make ranges which are dynamically loaded at run-time, add a second playable character, and so forth.
Is the conference in sport growth to depart these hard-coded values as arguments to set the coordinates or the angles of the transformable?
No, there is no such thing as a conference.
Additionally, I suppose how a lot hard-coding there may be will rely on the character of the item.
I am fairly sure some of us created HUDs fully by hard-coding values (coinCountLebel.place(screenSize.x() - 150, 0)) with the true need to come back again later and repair it earlier than launch, however yeah, they needed to ship.
Nevertheless, in case you are to make a stage by hard-coding your values, you will notice that you just’re spending quite a lot of time in compiling your sport simply since you moved an object just a few pixels.
