Blame the DOM?

🧑‍💻 Technical Support
1

I’m working on a project that uses two buttons to move back-and-forth (+|-) between a list of GLB files. My HTML works on a regular browser. When I apply the same programming to the 8th wall editor, I get a different response.

I’m guessing that it has to do with the DOM. In the original HTML, I reference the model via getElementByID. Then I replace the GLB using the same concept. Works fine with the HTML but fails in the editor.

The problem is as follows…
The HTML works fine when pressing +|-. If you advance one direction and then step back one, you end up on the original GBL. In the Editor, if you advance once, you get the next GLB. However, if you step back one, you get the GLB before the original.

Example…
D+1=E, E-1=D
vs
D+1=E, E-1=C, E+1=F, F-1=B
Hopefully, that makes sense.

Let me know if you have any thoughts on how to fix it.

2

can you share the code/logic you are using to do this?

Are you receiving any console errors or logs when this doesn’t work? Have you verified the button click in the editor with a log?

3

All good questions! In my post, I did not include any code because I didn’t have my computer with me. I should have my laptop back in a few days. I’ll post the code then.

As always, thank you Ian,

MC

4

I solved this problem shortly after I got help with my other issue “8th Wall Renderer Causing Issues.” (the link included below) It took me about 5 hours to make it work, but it works. I was looking at a JS Component concept and had to shift over to a HTML concept.

Thank you @Ian for your willingness to always help.

Thank You @Mal_Duffin

3 Likes
5

This topic was automatically closed 4 days after the last reply. New replies are no longer allowed.