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
*	Get collapsible menus working correctly.	Norwegian Rock Cat	2009-07-24	1	-1/+3
\| \| \| \| \| \| \| \| \| \|	There was an attempt to do this earlier, but it was a bit more complex than it needed to be. We now do the update on show in Cocoa. Carbon actually does it all for us, we just need to flip the bit. We may do the updates to often, but it's better than not enough. Task-Id: 195445 Reviewed-by: Denis
*	Update license headers as requested by the marketing department.	Jason McDonald	2009-06-16	1	-2/+2
\| \| \| \|	Reviewed-by: Trust Me
*	BT: Namespace compile fixes for Cocoa.	Norwegian Rock Cat	2009-04-15	1	-0/+6
\| \| \| \|	It worked in 4.5.0, so it should work in 4.5.1 too.
*	BT: Fix up comments in new Cocoa files.	Norwegian Rock Cat	2009-04-08	1	-42/+42
\| \| \| \| \| \|	It seems that Vim or Xcode or whatever I was using to paste these in messed up and added an extra space. Now we should be consistent with the .cpp files and I found a file that we missed too.
*	BT: Fix infinite recursion potential from change acff913a6287ad50b0ac782	Norwegian Rock Cat	2009-04-08	1	-4/+5
\| \| \| \| \| \| \| \|	It seems there is a potential for recursion because calling keyDown: can bubble up to the window which will start the process all over again. keyDown: will actually call qt_dispatchKeyEvent(), we may as well short it out here. All the previous cases I tried continue to work and we don't crash Creator if you are really impatient hitting keys.
*	BT: Send the keyevent after we send the shortcutoverride in menu	Norwegian Rock Cat	2009-04-07	1	-0/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	In our Cocoa menu we check if we need to send the key event to the qwidget before the menu has a chance at it, because logically in Qt, the key event should go to the widget and not the menubar first (a bit different than what happens on the mac). The way to determine this is to send a shortcut override event and see if it accepts it. If it does, that means we should just send it the key event. Previously we were sending the shortcut override, but not following through on the key event because we thought (however foolishly). That returning "YES" but not setting an action would somehow forward the event (it doesn't). There still seems to be some problems if you have a Dvorak-QWERTY+CWD layout, but this probably needs to be dealt with at the key mapper level. Reviewed-by: Prasanth Ullattil
*	Adjust comments	Norwegian Rock Cat	2009-04-07	1	-33/+34
\| \| \| \|	Someone messed up the whitespace on this comment.
*	Compile in Snow Leopard	Trenton Schulz	2009-03-24	1	-0/+4
\| \| \| \| \| \|	GCC 4.2 needs to have this extern (and likely every compiler != gcc 4. Reviewed-by: Trust Me
*	Long live Qt 4.5!	Lars Knoll	2009-03-23	1	-0/+187