PG editor templates

Bugs
1

image
image1950×220 31.4 KB

@Tricotou good ,morning! :smiley: :smiley:

2

:grin:
Seriously ? :see_no_evil: Do you mean you didn’t have the problem within 2 weeks and today it pops out ? :stuck_out_tongue: Still happening only on your MacOS I guess ?

3

Exactly.

However this time I was trying to edit an existing PG not starting a new one. Could it be that the existing PG contains some metadata or whatever which has triggered the issue again?

4

Seems unlikely. To me the playground has a unique source code version (from umd) and loads only the code inside the editor from the PG snippets server. But maybe I’m wrong on this.

@RaananW can you confirm that loading an old PG should not load any old code on the PG source code side ? :thinking:

Also, I make use of this ping to ask about this :
Since a few days, when I load a PG (let’s say https://playground.babylonjs.com/#4U4QH9#9 ) and then I save it, I get this URL : https://playground.babylonjs.com/?BabylonToolkit#4U4QH9#108 containing “BabylonToolkit” by default. Is it the new default behavior ? :thinking:

++
Tricotou

5

You are not wrong. The playground always uses the latest version of babylon, unless you force a specific version or a snapshot