Hi all, sorry that I am jumping towards this old thread.
I did get this weird issue in Maya 2018, where the
`dockCloseEventTriggered` is not called unless it is docked.
Tried using the 'dummy' method in the above post, but still, that signal is
not being called when undocked.
Wondering if
Hi,
I got the same error, but I found a way to get it to work...
What I do is before I create the widget that is going into the Workspace I
create a dummy one. I'm guessing that the bug is due to some initialization
that is not been done on the first Workspace created, here is the dummy
Can't get it to show on top anymore either. Always docks below the other
tabs
On Tue, Aug 15, 2017 at 11:08 AM, Erik Johansson-Evegård <
erik.johansson.eveg...@gmail.com> wrote:
> Whole interface goes crazy when running the code and sometimes selection
> do not work.
>
> On Tue, Aug 15, 2017 at
Whole interface goes crazy when running the code and sometimes selection do
not work.
On Tue, Aug 15, 2017 at 10:53 AM, Erik Johansson-Evegård <
erik.johansson.eveg...@gmail.com> wrote:
> Seems to still work like shit in maya 2018. Seriously.
>
> On Tue, Aug 8, 2017 at 4:13 AM, Michael Boon
Seems to still work like shit in maya 2018. Seriously.
On Tue, Aug 8, 2017 at 4:13 AM, Michael Boon wrote:
> I few days ago I ran a script from the Script Editor, which ran a robocopy
> from a network location, and contained a call to processEvents. It created
> an
I few days ago I ran a script from the Script Editor, which ran a robocopy
from a network location, and contained a call to processEvents. It created
an infinite loop of robocopy calls. I had to restart my PC to stop it!
On Tuesday, 8 August 2017 05:34:03 UTC+10, Cole O'Brien wrote:
>
> Gotcha,
Gotcha, yeah totally not a great solution in the long run. I had yet to find a
simple solution to this online, so I figured this would be helpful for those
that need something quick.
Thanks for the info though, I'll keep an eye out for bugs down the line.
--
You received this message because
Be very careful with your calls to processEvents(). In my experience it can
be a source of bugs if you do it without being aware of the effects. I have
seen situations where it happens in an event call stack which then causes
the event loop to run again and create a deeper stack. Then bugs can
For those googling this. I was able to solve this by connecting all signals on
my widget to a call to `QApplication.processEvents()`. Its not exactly elegant
but it got the job done.
Here's the basic code:
from Qt import QtWidgets
from Qt.QtCore import Signal, Slot
def
Actually, with a little more iteration I'm getting decent results by updating
the layout, and only that, on my main widget...
self.layout().update()
... via my event_queue that I mentioned earlier.
--
You received this message because you are subscribed to the Google Groups
"Python
Bummer. OK. I'll keep and eye out and repost if I find a proper solution.
For now, I have a workaround that is okay with my tool. Basically I have a
queue running in the background that collects callback messages from Maya. It
processes the queue when Maya is idle. This stuff like
Never solved it. Kinda giving up on maya and autodesk lately overall. Just
one of many things not working that should just work.
On Thu, May 18, 2017 at 12:28 AM, wrote:
> I'm noticing a similar defect myself and was scouring the interwebs to
> hopefully find an resolution.
12 matches
Mail list logo