Require name for objects tracked in vgl-namespace?

[vue-gl]

Require name for objects tracked in vgl-namespace?

[h-ikeda]

I thought that usually one camera and one scene are set, so it would be used conveniently without naming. But as you say, it might confuse...
To achieve both of them, I'd like to handle case of the camera or scene prop is undefined.

[unreal]

I thought that usually one camera and one scene are set, so it would be used conveniently without naming.

I figured that was your intent as well, but I think I saw one other issue where someone had a similar experience.

What about this:

In the case where a VglRenderer does not specify a camera, it checks the VglNamespace for cameras. If there is only one defined, it uses that one regardless of the camera's name. If there is more than one it throws an error saying that the camera prop is required when more than one camera is available.

I assume (but I'm not sure) that THREE.js will throw an error if the camera prop is passed in with an invalid camera name.

I also think it would be a good idea to add methods to VglNamespace for things like adding cameras, scenes, etc. to make sure the keys are not overwritten e.g. in the case where someone has two cameras with no name prop.

[h-ikeda]

Thank you for your suggestions.

to make sure the keys are not overwritten e.g. in the case where someone has two cameras with no name prop.

Sounds good, developer friendly.
I divided it to another issue to simplify tasks.

then,
TODO:

• VglRenderer should throw error when camera is undefined and two or more cameras exists.
• VglRenderer should use the any camera when camera is undefined and only one camera exists.
• same for scenes.
• check if an error is thrown when the specified (by name) camera does not exist.