1.9.6

Bugfix related to threading and IPC.

See #325 for details and thanks @nasefbasdf for fixing it!

1.9.5

Critical bugfixes for Maya 2018+ (seemingly worked fine under Maya 2017)

1.9.4

Blender Support

This release adds support for Blender.

The trick here is passing data between threads using a native Queue. A polling operator is added to Blender, which continuously polls a queue for things to do. When QML has a task for Blender, it's added to this queue, Blender runs it, and adds to another queue for QML to pick up the result.

It's currently running at 10 ms intervals, including when the GUI isn't visible, which isn't ideal and could be optimised away. E.g. stop polling when GUI is closed.

Remove Dependency on Qt from Host

This release removes the Qt dependency from a host, such that only the external Python process requires it.

Before, Qt was imported regardless of host, to try and show a splash screen, install an event filter and listen on the application quit signal. Now that only happens if Qt is available.

The Qt import mechanism itself was moved into a closed scope, such that it leaves mock-functions available for hosts that lack access to Qt. The result is no loss in functionality, and no need for PyQt5 to exist from a given host. Now all you need is love. And Python.

PYTHONPATH

It also removes the need for PyQt5 to exist on PYTHONPATH, which can complicate this scenario:

1. Pyblish QML uses Python 3, from a Python 2 host without access to Qt, e.g. Blender
2. PyQt5 is installed to the target Python 3's site-packages

In the above case, one would need to append Python 3's site-packages to the PYTHONPATH of the given host, which would give Python 2 access to its modules. The "proper" was of handling this is to not install PyQt5 in site-packages, but elsewhere, e.g. /special/pyqt5/path such that only that path could be added to PYTHONPATH.

Now you don't need to do that either.

1.9.3

Improved support for erroneous environments on the Linux operating system.

Before, all of the environment was inherited by QML, resulting in variables such as PYTHONHOME dictating where the child Python process found refuge and native libraries. In some settings, those could conflict with the given Python environment and cause Pyblish QML to fail to load.

With this release, only the bare essentials of an environment is inherited, similar to how it previously also worked under Windows.

1.9.2

Bug fix release.

Misplaced pulse thread which causing QML closing itself after launched 15 seconds when modal mode is on.
See #319

Thanks to @renaudll !

1.9.1

Bugfix release

• Fix #309
• Fix #281 related bug

Please see #314 for detail :)

1.9.0

Deprecating Foster Mode

This release dropped the optional ability to embed pyblish-qml window from subprocess into the host (e.g. Maya), the feature was called Foster Mode (since it's fostering subprocess window), which was an experimental feature introduced since v1.8.0.

Other feature or fix, which implemented after v1.8.0 will remain the same.

For more detail, see this PR #312.

Thanks :)

1.8.7

Bugfix release

• See #306 for details.

1.8.6

• Fix #281
  Now toggling Plugins and Instances from sections can get an instant feedback.
  Thanks to @asztalosdani

• Fix #274, #119
  Each publishing state now have their own message display on GUI.

• Fix #283
  The checkbox of Plugins and Instances will not stay solid when it's off.

• Implement #302
  Instances are able to optionally group by arbitrary string, not only family.
  Thanks to @darkvertex

  

1.8.5

This release fixed one issue:

• Plugins' action menu may have some uncleaned items if there are multiple Category or Separator.

See #300 for more detail.

Thanks !