These are general settings which affect polyscope’s behavior as a library. It is often convenient to set them just before calling
polyscope::init, but they may set be anywhere.
#include "polyscope/polyscope.h" // a few options polyscope::options::programName = "important app"; polyscope::options::verbosity = 0; polyscope::options::usePrefsFile = false; // initialize polyscope::init();
A general name to use when referring to the program in window headings, etc. Default:
polyscope::options::programName = "important app";
How much useful info should polyscope print to
>= 2print a lot
polyscope::options::verbosity = 1;
A string used as a prefix for all messages printed to the terminal by polyscope. Default:
polyscope::options::printPrefix = "[MYAPP] "; // prints now look like "[MYAPP] loaded openGL"
errors throw execptions
If true, errors in polyscope throw execptions. If false, a
polyscope::error is shown in the UI, but processing attempts to continue. Default:
The main loop will not run at more than
maxFPS iterations per second.
-1 disables, running the loop as fast as possible. Default:
use prefs file
Polyscope can read and write to a preferences file to save state between invocations. For now, this is primarily used to restore the window position on the desktop. The preference file is a
json-formatted plaintext file called
This option controls the use of the preferences file. If
false, if will be neither written nor read. Default:
Polyscope is designed to use lazy rendering: the scene is only re-drawn if it has changed since the last time it was drawn. This can dramatically reduce resource consumption, and keeps the immediate GUI responsive even on scenes which are irresponsibly large for the machine’s graphics capabilities.
If this option is
true, the scene will be redrawn on every main loop iteration no matter what, circumventing the lazy drawing features. Default:
open imgui window for user callback
If true, an ImGui window will be created and docked to the side of the UI when the user callback function is invoked. This means you can immediately start making ui calls like
If false, no ImGui anything will be pushed on the stack when the callback is invoked, and the user is entirely responsible for making any ImGui calls (or not making any).
invoke user callback for nested show
Suppose you call
polyscope::show(), and within your callback, another instance of
polyscope::show() is called—this is a nested show.
Depending on the situation, you might or might not want your
userCallback to continue being executed on each render loop iteration of this nested viewer; this setting exposes the option.
If true, your callback will be executed as normal for every main loop iteration, even in nested show windows.
If false, your callback will only be executed for initial, outermost calls to
render error checks
If true, the rendering subsystem will eagerly check for and report errors. This comes at some small performance cost, but can help catch problems.
true when compiled in