This just updates the config and saves it to `flamenco-manager.yaml`.
Saving the configuration doesn't restart the Manager yet, that's for
another commit.
This adds a `-wizard` CLI option to the Manager, which opens a webbrowser
and shows the First-Time Wizard to aid in configuration of Flamenco.
This is work in progress. The wizard is just one page, and doesn't save
anything yet to the configuration.
Adjust the loading of BAT from a wheel file in such a way that all
submodules are loaded in one go. This ensures that they're still
isolated from the rest of Blender (so other add-ons won't find our BAT),
but not from each other (so that there is only one copy of each
submodule).
In practice, this solves an issue where calling
`blender_asset_tracer.blendfile.set_strict_pointer_mode(False)` had no
effect. This was caused by each loaded submodule having a different copy
of `blendfile`.
Also loaded modules are logged more explicitly (at INFO level) to aid in
debugging later on.
Add instructions to `web/README-static.md`, describing how to run the
static flamenco.io website locally.
Reviewed By: sybren
Differential Revision: https://developer.blender.org/D15426
Due to issues with library overrides and unsynced pointers, it's quite
common for the Blender Animation Studio to get "address unknown" errors
from BAT. To avoid these, Strict Pointer Mode is disabled.
This way, on OS that allow it, Flamenco can be added as home shortcut
and have the proper shortcut name, icon, theme color, and browser buttons.
Needs testing on how 'standalone' display looks on Android tablets. Perhaps
a more minimal version of the browser can be used instead ('minimal-ui').
This operation takes the platform & audience, and returns the variables
that are applicable for that combination. This can then be used by the
web frontend or by the Blender add-on to do variable replacement.
Reload the webapp 60 minutes after keyboard/mouse activity.
Previously this was a hard 60 minutes after the webapp was loaded, which
means that it could happen while someone was actively working in the web
interface. This should now be prevented.
Use overlay overflow for compatible browsers (e.g. Chromium),
fallback to auto for non-compatible browsers (e.g. Firefox).
There should be no visible changes for Firefox users (tested on 101.0.1).
