ParaView/Developer Info: Difference between revisions
From KitwarePublic
< ParaView
Jump to navigationJump to search
| Line 10: | Line 10: | ||
to determine when it should play the next testing event. If that busy lock is running when your code calls processEvents it will cause the tests to start playing, which will break the test. | to determine when it should play the next testing event. If that busy lock is running when your code calls processEvents it will cause the tests to start playing, which will break the test. | ||
The solution is dependent on where you need to call processEvents. | The solution is dependent on where you need to call processEvents. | ||
pqCoreUtilities::processEvents( | pqCoreUtilities::processEvents(); | ||
pqEventDispatcher::processEvents( | pqEventDispatcher::processEvents(); //only in Widgets since widgets can't depend on core | ||
Both methods support the QEventLoop::ProcessEventsFlags flags argument. For more information on processEvents please see the [http://doc.qt.nokia.com/4.7/qcoreapplication.html#processEvents Qt Documentation] | |||
== Debugging == | == Debugging == | ||
== Environment Flags == | == Environment Flags == | ||
Revision as of 14:01, 6 May 2011
This is a general collection of knowledge for ParaView developers.
VTK Development
Proxy Development
Qt Development
QApplication::processEvents()
Because of the testing framework we are unable to safely use processEvents. The testing framework has a busy lock it uses to determine when it should play the next testing event. If that busy lock is running when your code calls processEvents it will cause the tests to start playing, which will break the test. The solution is dependent on where you need to call processEvents.
pqCoreUtilities::processEvents(); pqEventDispatcher::processEvents(); //only in Widgets since widgets can't depend on core
Both methods support the QEventLoop::ProcessEventsFlags flags argument. For more information on processEvents please see the Qt Documentation
