# SMTK's ParaView plugins

**URL:** https://discourse.kitware.com/t/smtks-paraview-plugins/728
**Category:** Design
**Created:** [October 21, 2021, 2:41am UTC](https://discourse.kitware.com/t/smtks-paraview-plugins/728 "2021-10-21T02:41:19Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![dcthomp](https://discourse.kitware.com/user_avatar/discourse.kitware.com/dcthomp/32/10_2.png) [@dcthomp](https://discourse.kitware.com/u/dcthomp)
#### Post date: [October 21, 2021, 2:41am UTC](https://discourse.kitware.com/t/smtks-paraview-plugins/728/1 "2021-10-21T02:41:19Z")

</div>

Until [ParaView MR 5283](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/5283), plugins that want functions invoked upon load were required to use the `pqAutoStartInterface` which (as you can infer from the class name) requires Qt. Recently, Paraview got more careful about loading plugins in python scripts when no GUI was present, meaning that this method would leave `pvpython` scripts with no way to ensure a plugin was properly initialized.

For SMTK, this meant that `Manager` instances were never passed to `Registrar` classes when running `pvpython` – so resource types, operations, views, etc. were not made available.

In the next few days, the ParaView MR and a [matching SMTK MR](https://gitlab.kitware.com/cmb/smtk/merge_requests/2570) will be merged and [offline python scripting with SMTK](https://discourse.kitware.com/t/using-the-python-interpreter-included-with-cmb-and-aevacmb/) will start working again.
