Add some test scripts

...and start supporting // comments when loading commands via prgload (we
already support this in the autoexec.drgscr, no reason not to do it for
other files)

Retyping is boring, and what's more important these also show concepts
that a higher level API or a new editor implementation would use to
manage the scene contents.

Change-Id: Iefbe8efee47c475b91efe5b05602eb18b9749791
Reviewed-by: Andy Nichols <andy.nichols@qt.io>

1 files changed, 16 insertions, 0 deletions

diff --git a/tests/scripts/dynscene_2.drgscr b/tests/scripts/dynscene_2.drgscr
new file mode 100644
index 0000000..78bd322
--- /dev/null
+++ b/tests/scripts/dynscene_2.drgscr
@@ -0,0 +1,16 @@
+// Assuming dynscene_1 has run, this shows how the mesh and materials could get replaced for a model
+
+// Temporarily disconnect from the scene
+setparent(kube, null)
+
+// Remove old material children
+kill(ka)
+
+// Add new ones (no point in this example since the old and new mesh both have 1 submesh but shows the concept)
+object(ka, ka, DefaultMaterial, kube, Slide1)
+
+// Change the mesh
+set(kube, sourcepath, #Sphere)
+
+// Reconnect to scene
+setparent(kube, Layer)