mottosso on master
Update Travis for automatic dep… (compare)
mottosso on master
Update Travis for automatic dep… (compare)
loonghao on 0.1.0
loonghao on master
First commit Improve readme Improve readme and 4 more (compare)
bpy.app.timers.register
method as it is easy to implement in Gaffer's existing EventLoop, however I think it is interfering with Blender's opengl context somehow (debugger says it is crashing in some opengl code of Blender) :(
trying out
bpy.app.timers.register
method as it is easy to implement in Gaffer's existing EventLoop, however I think it is interfering with Blender's opengl context somehow (debugger says it is crashing in some opengl code of Blender) :(
Are you using Blender operators in the Qt app? That could also cause crashes if the context
is incorrect. I haven't checked it recently, but that's why I am still using a modal operator to run the Avalon Qt apps inside of Blender.
DRW_opengl_context_enable();
and followed what other DCC apps do (Maya/Houdini) to get the OpenGL context, so I tried wrapping it in python and call it in GLWidget, but that kinda deadlocks things, I am pretty sure it is Gaffer nuking the existing GL context on that thread rather than just sharing the one with Blender
@chadmv Regarding Pyblish examples maybe this link could be worthwhile. They are not focused on Pyblish per se but on Avalon, but they all run publishing with Pyblish... so they might have some extra "pipeline things" but the publishing all runs through Pyblish.
I believe most of those avalon configs have the code laid out so that the Pyblish plug-ins are somewhere in {config}/plugins/{host}/publish
- for example like this (maya). or this (maya) or this (houdini).
show
function, call each line yourself until you hit the point whereby it hangs
show
def _install():
# Default order (customise order and content via QT_PREFERRED_BINDING)
default_order = ("PyQt5", "PySide2", "PySide", "PyQt4")
preferred_order = list(
b for b in QT_PREFERRED_BINDING.split(os.pathsep) if b