To properly isolate the renderer, which is going to be relatively complex, from the rest of the core, I have decided to create a separate directory for it. The code there is pretty much empty, but the structure and most of the classes/structs are already there. The room traversal algorithm is there, though.
The idea moving onwards is to have a RoomBuilder that accepts a 2D tile array (fresh from the editor :D) and "bakes" it into a Room tree to be processed efficiently by the Renderer.
Regarding the fopen_s change / revert, in order to be standards compliant, it has to be kept changed to fopen. Thus, to remove the warning, it should just be suppressed (there are many ways to do so, like the ones I have personally commented to you).
And from now on, I would really appreciate if, when new files are added, they are also listed in its corresponding CMakeLists.txt, for faster progress (;
To properly isolate the renderer, which is going to be relatively complex, from the rest of the core, I have decided to create a separate directory for it. The code there is pretty much empty, but the structure and most of the classes/structs are already there. The room traversal algorithm is there, though.
The idea moving onwards is to have a RoomBuilder that accepts a 2D tile array (fresh from the editor :D) and "bakes" it into a Room tree to be processed efficiently by the Renderer.
Regarding the
fopen_schange / revert, in order to be standards compliant, it has to be kept changed tofopen. Thus, to remove the warning, it should just be suppressed (there are many ways to do so, like the ones I have personally commented to you).And from now on, I would really appreciate if, when new files are added, they are also listed in its corresponding CMakeLists.txt, for faster progress (;
Worked on it for 1 hour (11 to 12, on GMT+1).