Qt.git - Qt s a cross-platform application framework that is used for developing application software that can be run on various software and hardware platforms with little or no change in the underlying codebase, while still being a native application with native capabilities and speed.

	Commit message (Collapse)	Author	Age	Files	Lines
*	Cleanup our usage of the term "Qt Software".	Jason McDonald	2009-06-16	1	-1/+1
\| \| \| \|	Reviewed-by: Trust Me
*	Update license headers as requested by the marketing department.	Jason McDonald	2009-06-16	53	-106/+106
\| \| \| \|	Reviewed-by: Trust Me
*	Fix more NaNs in Elastic Nodes example	João Abecasis	2009-04-22	1	-3/+6
\| \| \| \| \| \| \|	Don't try to draw zero-length lines. Don't draw lines if nodes are superimposed. Reviewed-by: Andreas
*	BT: Fix lock-up & crash in the Elastic Nodes example	Andreas Aardal Hanssen	2009-04-21	1	-3/+8
\| \| \| \| \| \| \| \|	Ensure that we don't divide by 0 when two nodes are exactly on top of each other. Reviewed-by: Alexis Reviewed-by: Joao
*	BT: Adjust the colliding mice example to work with coalesced updates.	Norwegian Rock Cat	2009-04-06	3	-7/+9
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	It seems that Cocoa is much more strict about coalesced updates than Carbon ever was. The upshot of this is that some examples that "worked" after a fashion in Carbon, do not exhibit good frame rates with Cocoa. The reason why is that apparently Cocoa will decide to flush to the screen every time a timer fires. If you have a lot of timers that are all dependent on doing on update to the screen, you will get undesirable effects. Thankfully, it is possible to adjust the examples to follow best practices and get a good result. So, we now only do the animation once using QGraphicsScene::advance(). We are also able to make the mice less heavy (no QObject subclass). I've updated the docs and someone on the doc team has kindly volunteered to go through them. Reviewed-by: Andreas
*	Long live Qt 4.5!	Lars Knoll	2009-03-23	272	-0/+9535