Comments on: Using Xerces-C++ Progressive Scan with Qt http://thesmithfam.org/blog/2006/11/12/using-xerces-c-progressive-scan-with-qt/ Your blog is probably better than mine. Wed, 19 Nov 2008 04:55:59 +0000 http://wordpress.org/?v=2.6.3 By: Sajjad http://thesmithfam.org/blog/2006/11/12/using-xerces-c-progressive-scan-with-qt/#comment-62506 Sajjad Fri, 31 Oct 2008 22:02:11 +0000 http://thesmithfam.org/blog/2006/11/12/using-xerces-c-progressive-scan-with-qt/#comment-62506 Quite a good suggestion I was wondering if Xerces could be used to generate xml content from the GUI component...like the SceneGraph Structure in the GUI representation Quite a good suggestion

I was wondering if Xerces could be used to generate xml content from the GUI component…like the SceneGraph Structure in the GUI representation

]]> By: Byron Clark http://thesmithfam.org/blog/2006/11/12/using-xerces-c-progressive-scan-with-qt/#comment-2423 Byron Clark Mon, 13 Nov 2006 23:41:57 +0000 http://thesmithfam.org/blog/2006/11/12/using-xerces-c-progressive-scan-with-qt/#comment-2423 I'm not sure about that definition, unless it's a QT4 thing. The QT3 docs for QTimer say: "As a special case, a QTimer with timeout 0 times out as soon as all the events in the window system's event queue have been processed." That seems pretty consistent with what other toolkits count as idle time. I’m not sure about that definition, unless it’s a QT4 thing. The QT3 docs for QTimer say:

“As a special case, a QTimer with timeout 0 times out as soon as all the events in the window system’s event queue have been processed.”

That seems pretty consistent with what other toolkits count as idle time.

]]> By: Dave http://thesmithfam.org/blog/2006/11/12/using-xerces-c-progressive-scan-with-qt/#comment-2384 Dave Mon, 13 Nov 2006 03:50:31 +0000 http://thesmithfam.org/blog/2006/11/12/using-xerces-c-progressive-scan-with-qt/#comment-2384 It should probably be noted that "idle" in Qt has a different meaning than in, say, wxWidgets. If you specify a 0 ms interval on a QTimer, the timer will fire over and over, even if the GUI is not idle. Qt will squeeze timer events in whenever it can, even between paint events and user input events. In wxWidgets, the idle event only fires once the application becomes idle, and does not fire again until the app goes from non-idle to idle. It should probably be noted that “idle” in Qt has a different meaning than in, say, wxWidgets. If you specify a 0 ms interval on a QTimer, the timer will fire over and over, even if the GUI is not idle. Qt will squeeze timer events in whenever it can, even between paint events and user input events. In wxWidgets, the idle event only fires once the application becomes idle, and does not fire again until the app goes from non-idle to idle.

]]> By: Byron Clark http://thesmithfam.org/blog/2006/11/12/using-xerces-c-progressive-scan-with-qt/#comment-2379 Byron Clark Mon, 13 Nov 2006 02:32:33 +0000 http://thesmithfam.org/blog/2006/11/12/using-xerces-c-progressive-scan-with-qt/#comment-2379 Note that the 0 ms timeout on the QTimer really means run whenever idle. I always wondered how to do that in QT. Note that the 0 ms timeout on the QTimer really means run whenever idle. I always wondered how to do that in QT.

]]>