Any GUI Framework generally blockwaits on single System call which may multiplex number of soft interfaces. But Qt has two kinds of events viz External events triggered by user through Keyboard & Mouse/Touch screen received by QSocketNotifiers and internal events triggered by QTimers.
Both are being processed sequentially, none of them can be blocking type. Then CPU utilization should be high enough because exec call doesnt yield CPU at all. But it is verified that Qt Applications on Embedded platform is not taking so much of CPU. "select" call used by Qt is not passing NULL for timeout parameter anywhere in source code. Immediately it is looking for any timeouts of Qtimers and is repeating in while loop as long as running.
Then how CPU utilization is fairly Low????
Please explain me where Qt is block-waiting for or How CPU utilization is LOW enough???
Bookmarks