Environment Variables¶
You can configure how bqt is running through feature toggles exposed as Environment variables.
These toggles are used by setting them to either "0" or "1".
BQT_DISABLE_STARTUP¶
added in 1.0.0
Disable bqt. Setting this to "1" will ensure that bqt is not managing Blender windows.
No Qt application should be expected to work.
BQT_DISABLE_WRAP¶
added in 1.3.1
Set this to "1" to disable wrapping any Blender window in a QWindow.
If this is set to "1" bqt will use and internal system (bqt.manager)
to handle windows always being on top.
BQT_DISABLE_CLOSE_DIALOGUE¶
added in 1.0.0
Do not use bqt close dialog.
Qt Windows are always above Blender, this means that if this is enabled the close dialog might appear behind Blender.
BQT_MANAGE_FOREGROUND¶
added in 1.2.2
If BQT_DISABLE_WRAP is enabled bqt still tries to display any
widget or window above the Blender window.
Set this to "0" to stop bqt from trying to display Windows above the Blender window.
BQT_AUTO_ADD¶
added in 1.2.0
By default, bqt handles parenting of any orphaned window. This means that you don't have to explicitly set the parent of a tool. bqt will pick it up as an orphan and set itself as the parent.
If disabled, set to "0", any top level window won't automatically be added to bqt,
any orphaned will be garbage collected. You need to set the parent
explicitly to keep the tool around.
BQT_UNIQUE_OBJECTNAME¶
added in 1.3.0
By default, bqt will ensure only one of each object name is available. This will ensure that opening your tool a second time will not open a new window, but instead it will surface the old instance.
Set this to "0" to disable this behavior.
BQT_DOCKABLE_WRAP¶
added in 1.3.1
Set to "0" to disable wrapping of widgets in a dockable widget.
By default, bqt grabs all orphaned widgets, wraps them in a window,
and parents them to the main window.
This means that you don't have to manually fetch the main window and
parent your tool to it. However, this also means that if you unparent
a widget by setting parent(None) on it
(like you would if removing dynamically spawned widgets)
the widget will be grabbed by bqt and parented to the main window again.
BQT_LOG_LEVEL¶
added in 1.4.1
By default, bqt does not surface any logs.
Set to "DEBUG", "INFO", "WARNING", "ERROR", "CRITICAL"
to surface logs of the set level and higher.