You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Window class has a default arcball camera that is very useful, but sometimes starts out in a position that's a bit too close to the geometry.
Right now, it's a private member of the Window class, and not to my knowledge accessible from outside. Would it be possible to allow outside code to access it and move it around?
The text was updated successfully, but these errors were encountered:
There was a PR that asked for this (#209), and my reply to it was:
I believe the canonical way to do it is to construct your own camera or use one of kiss3d::camera::* and pass it to Window::render_with_camera instead of calling Window::render. Alternatively, you can create a type and have it implement kiss3d::window::State which allows you to return your own camera in State::cameras_and_effect_and_renderer, then use Window::render_loop to start the rendering.
This is still my viewpoint today as it not only does the same thing, but also easier to handle than borrowing from the Window.
Hello!
The Window class has a default arcball camera that is very useful, but sometimes starts out in a position that's a bit too close to the geometry.
Right now, it's a private member of the Window class, and not to my knowledge accessible from outside. Would it be possible to allow outside code to access it and move it around?
The text was updated successfully, but these errors were encountered: