You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now, all the scene configuration remain at the Sandbox constructor body. Every time a new test configuration is required the previous one is commented. In this issue we want to add a mechanism that stores all the scene configurations and loads each by one call.
Best if the call was compilation-independent, I mean there is a parameter in the program execution line that tells which configuration is to be applied during generation of the scene.
EDIT
After merging #44 we want to select different scenes without any recompilation. So the input in the execution line should be the scene's file name from BartaEngineSandbox/scenes.
The text was updated successfully, but these errors were encountered:
Bartanakin
added
Easy
Scale of knowledge of the project requirement
Quick
Scale of workload requirement
and removed
Medium
Scale of knowledge of the project requirement
Time-demanding
Scale of workload requirement
labels
Mar 1, 2025
Now, all the scene configuration remain at the
Sandbox
constructor body. Every time a new test configuration is required the previous one is commented. In this issue we want to add a mechanism that stores all the scene configurations and loads each by one call.Best if the call was compilation-independent, I mean there is a parameter in the program execution line that tells which configuration is to be applied during generation of the scene.
EDIT
After merging #44 we want to select different scenes without any recompilation. So the input in the execution line should be the scene's file name from
BartaEngineSandbox/scenes
.The text was updated successfully, but these errors were encountered: