There needs to be more clearly defined rules for wrapping around of data, at the moment is is based off how python implements it in lists: you can go negative to go backwards off the list. So going off the start of the canvas will display at the end, but going off the end will disappear, and going wrapping to the end twice doesn't work. Another problem is that this is not consistent, for example the collision detection doesn't wrap, this is a major problem. This is demonstrated in terrain.py.
I need to decide whether to support wrapping, in which case it needs to work perfectly infinitely, or it should not work at all. If I were to enable it, it should be toggle-able like the border and center attributes for the canvas, and maybe there should be an option for scrolling too?
There needs to be more clearly defined rules for wrapping around of data, at the moment is is based off how python implements it in lists: you can go negative to go backwards off the list. So going off the start of the canvas will display at the end, but going off the end will disappear, and going wrapping to the end twice doesn't work. Another problem is that this is not consistent, for example the collision detection doesn't wrap, this is a major problem. This is demonstrated in terrain.py.
I need to decide whether to support wrapping, in which case it needs to work perfectly infinitely, or it should not work at all. If I were to enable it, it should be toggle-able like the border and center attributes for the canvas, and maybe there should be an option for scrolling too?