add small missing docs for windows, cameras, ui scale, quantity removal

Author: nmwsharp

cpp/source/basics/camera_controls.md

@@ -4,6 +4,9 @@ These functions control the current viewing camera in for the Polyscope scene, a
 ```cpp
 #include "polyscope/polyscope.h"
 
+// set the size of the window
+polyscope::view::setWindowSize(600, 800);
+
 // change the default up-direction or front-direction for the scene
 polyscope::view::setUpDir(polyscope::UpDir::ZUp);
 polyscope::view::setFrontDir(polyscope::FrontDir::NegYFront);
@@ -34,6 +37,35 @@ polyscope::view::setCameraParametersForCurrentView(cam_params):
 polyscope::CameraView* cam = polyscope::registerCameraView("cam1", params) 
 ```
 
+## Window Controls
+
+Get and set the size of the window which appears on the user's display.
+
+??? func "`#!cpp void view::setWindowSize(int width, int height)`"
+
+    Set the size of the window.
+
+    Note that for some platforms, on high-DPI screens the pixel buffer resolution may be different from the logical size. This is the logical size.
+
+??? func "`#!cpp std::tuple<int, int> getWindowSize()`"
+
+    Get the current size of the window.
+
+    Note that for some platforms, on high-DPI screens the pixel buffer resolution may be different from the logical size. This is the logical size.
+
+??? func "`#!cpp std::tuple<int, int> getBufferSize()`"
+
+    Get the current pixel buffer resolution of the window.
+
+    Note that for some platforms, on high-DPI screens the pixel buffer resolution may be different from the logical size. This is the pixel buffer size.
+
+??? func "`#!cpp void view::setWindowResizable(bool newVal)`"
+
+    If `false`, the window will be locked to size and the OS will not allow it to be resized. (Default: `true`)
+
+    There is also a corresponding `getWindowResizable()`.
+
+
 ## Manipulating the Current View
 
 These settings affect the 3D camera view in polyscope. It is often convenient to set them just before calling `polyscope::init()`, but they may set be anywhere.

cpp/source/basics/program_options.md

@@ -126,6 +126,22 @@ polyscope::init();
 
     If this option is `true`, the scene will be redrawn on every main loop iteration no matter what, circumventing the lazy drawing features. Default: `false`.
 
+??? func "`#!cpp float options::uiScale`"
+    
+    ##### ui scale
+
+    A scale factor for all UI elements (text, buttons, panels). Can be useful for increase font sizes on high DPI screens. `2.0` means make everything twice as large.
+
+    This factor should also be incorporated into any user-defined widths in custom UIs, to ensure spacing remains correct as scaling is changed, like:
+
+    ```
+    ImGui::PushItemWidth(100 * polyscope::options::uiScale);
+    ```
+
+    If `-1`, a sensible value will be guessed at initialization time. This value is saved and restored between settings if the preferences file is enabled.
+
+    Default: `-1.`
+
 ??? func "`#!cpp bool options::buildGui`"
 
     ##### build gui

cpp/source/structures/structure_management.md

@@ -88,6 +88,22 @@ If no longer needed, structures can be removed by name or by pointer. Removing a
 
     Remove all structures from the scene.
 
+## Quantities
+
+Quantities, like scalar functions, color fields, vector fields, and more, can be associated with structures. See the available options for each kind of structure.
+
+Quantities can be removed from a structure by name.
+
+??? func "`#!cpp void Structure::removeQuantity(std::string name, bool errorIfAbsent = false)`"
+
+    Remove a quantity from the structure by name.
+
+
+??? func "`#!cpp void Structure::removeAllQuantities()`"
+
+    Remove all quantities which have been added to the structure.
+
+
 ## Structure options
 
 These basic options are shared by all structures.  Structure options are managed as [persistent values]([[url.prefix]]/basics/parameters/#persistent-values), and thus will persist if a new structure is registered with the same name.

py/source/basics/camera_controls.md

@@ -35,6 +35,35 @@ ps.set_view_camera_parameters(cam_params)
 ps_cam = ps.register_camera_view("cam1", cam_params) 
 ```
 
+## Window Controls
+
+Get and set the size of the window which appears on the user's display.
+
+??? func "`#!python set_window_size(width, height)`"
+
+    Set the size of the window.
+
+    Note that for some platforms, on high-DPI screens the pixel buffer resolution may be different from the logical size. This is the logical size.
+
+??? func "`#!python get_window_size()`"
+
+    Get the current size of the window. Returns a `(width, height)` tuple.
+
+    Note that for some platforms, on high-DPI screens the pixel buffer resolution may be different from the logical size. This is the logical size.
+
+??? func "`#!python get_buffer_size()`"
+
+    Get the current pixel buffer resolution of the window. Returns a `(width, height)` tuple.
+
+    Note that for some platforms, on high-DPI screens the pixel buffer resolution may be different from the logical size. This is the pixel buffer size.
+
+??? func "`#!python set_window_resizable(is_resizable)`"
+
+    If `false`, the window will be locked to size and the OS will not allow it to be resized. (Default: `true`)
+
+    There is also a corresponding `get_window_resizable()`.
+
+
 ## Manipulating the Current View
 
 These settings affect the 3D camera view in polyscope. It is often convenient to set them just before calling `ps.init()`, but they may set be anywhere.

py/source/basics/program_options.md

@@ -130,6 +130,25 @@ ps.init()
 
     If this option is `True`, the scene will be redrawn on every main loop iteration no matter what, circumventing the lazy drawing features. Default: `False`.
 
+??? func "`#!python set_ui_scale(scale)`"
+    
+    ##### ui scale
+
+    A scale factor for all UI elements (text, buttons, panels). Can be useful for increase font sizes on high DPI screens. `2.0` means make everything twice as large.
+
+    There is also a corresponding `get_ui_scale()`.
+
+    This factor should also be incorporated into any user-defined widths in custom UIs, to ensure spacing remains correct as scaling is changed, like:
+
+    ```
+    psim.PushItemWidth(100 * ps.get_ui_scale());
+    ```
+
+    If `-1`, a sensible value will be guessed at initialization time. This value is saved and restored between settings if the preferences file is enabled.
+
+    Default: `-1.`
+
+
 ??? func "`#!python set_build_gui(b)`"
 
     ##### build gui

py/source/structures/structure_management.md

@@ -67,6 +67,23 @@ ps.remove_all_structures()
     Remove all structures from the scene.
 
 
+## Quantities
+
+Quantities, like scalar functions, color fields, vector fields, and more, can be associated with structures. See the available options for each kind of structure.
+
+Quantities can be removed from a structure by name.
+
+
+??? func "`#!python Structure.remove_quantity(name, error_if_absent=False)`"
+
+    Remove a quantity from the structure by name.
+
+
+??? func "`#!python Structure.remove_all_quantities()`"
+
+    Remove all quantities which have been added to the structure.
+
+
 ## Structure options
 
 These basic options are shared by all structures.  Structure options are managed as [persistent values]([[url.prefix]]/basics/parameters/#persistent-values), and thus will persist if a new structure is registered with the same name.