Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ArcballControls: Derive from Controls. #29109

Merged
merged 1 commit into from
Aug 10, 2024
Merged

ArcballControls: Derive from Controls. #29109

merged 1 commit into from
Aug 10, 2024

Conversation

Mugen87
Copy link
Collaborator

@Mugen87 Mugen87 commented Aug 10, 2024

Related issue: #29085

Description

Same as #29085.

@Mugen87 Mugen87 added this to the r168 milestone Aug 10, 2024
@Mugen87 Mugen87 merged commit c8f8707 into mrdoob:dev Aug 10, 2024
11 checks passed
@s-rigaud
Copy link
Contributor

s-rigaud commented Aug 11, 2024

@Mugen87 Simple suggestion, as every control from examples/jsm/controls use camera as the first parameter of instantiation. Shouldn't the first parameter of base class Controls be called "camera" instead of "object" ?

this.object = object;

@Mugen87
Copy link
Collaborator Author

Mugen87 commented Aug 12, 2024

Thought about this as well^^. I've though it's more safe to use the generic name object if a control only manipulates a 3D object like a mesh. I wonder know if such an implementation would still require a reference to the scene's camera though...

@s-rigaud
Copy link
Contributor

As there is 9 implementations of controls in the examples folder and we are not sure that even a new special control focus on a single mesh will not need the camera, wouldn't it be better to rename it now that not all the controls are using base class Controls instead of having to rename the attribute later on all the controls ? 🤔

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants