*الدار العربية للتنمية الإدارية*
*بالتعاون مع الإتحاد الدولى لمؤسسات التنمية البشرية*
*الدورة التدريبية *
*الرقابة المالية فى الجهات الحكومية *
*القاهرة – ماليزيا *
*خلال الفترة من **15 ** الى **19**أكتوبر 2017 م*
*تهدف الورشة الى *
*التعرف على الأساليب والنظم الحديثة في مجال الرقابة المال
Really? How'd he fit the grapefruit up there?
"There are no dumb questions" - Carl Sagan.
> On Aug 7, 2017, at 04:04, nour hamdy wrote:
>
>
> الدار العربية للتنمية الإدارية
> بالتعاون مع الإتحاد الدولى لمؤسسات التنمية البشرية
> الدورة التدريبية
> الرقابة المالية فى الجهات الحكومية
> القاهرة –
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 connectToReload(MyWindow)
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 eith
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 y
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,
