summaryrefslogtreecommitdiffstats
path: root/src/gui
Commit message (Collapse)AuthorAgeFilesLines
* Add the complex control SC_SpinBoxEditField to style optionNils Christian Roscher-Nielsen2009-07-091-1/+1
| | | | Reviewed-by: Thierry
* Compile fix.Denis Dzyubenko2009-07-091-0/+1
|
* Fix compile issueThierry Bastian2009-07-093-13/+20
|
* QTabBar: now uses QVariantAnimation over QTimeLineThierry Bastian2009-07-094-73/+65
| | | | QTimeLine is now no more used in private APIs
* QTreeView: cleanup of useless private slotsThierry Bastian2009-07-094-48/+20
| | | | currentChange is slot in the public class (QAbstractItemView
* QTreeView: use QVariantAnimation over QTimeLineThierry Bastian2009-07-094-67/+55
|
* Remove unneeded assert.Friedemann Kleint2009-07-091-1/+0
| | | | | Triggered on Designer startup on Linux. Acked-by: Thierry Bastian <thierry.bastian@nokia.com>
* Directly copy QGenericMatrix members instead of using qMemCopy()Rhys Weatherley2009-07-091-1/+3
| | | | | | | | Using qMemCopy limits QGenericMatrix to plain old types like float and double. Copying the values normally will allow copy constructors to work on non plain types. Reviewed-by: trustme
* Remove some left-over mentions of fixed-point in math3dRhys Weatherley2009-07-095-20/+3
| | | | Reviewed-by: trustme
* Make compileBill King2009-07-081-0/+1
|
* Merge commit 'origin/4.5'Bill King2009-07-088-80/+83
|\ | | | | | | | | | | | | | | | | | | Conflicts: src/sql/drivers/ibase/qsql_ibase.cpp tests/auto/q3sqlcursor/tst_q3sqlcursor.cpp tests/auto/qsqldatabase/tst_databases.h tests/auto/qsqldatabase/tst_qsqldatabase.cpp translations/qt_ru.ts
| * Update QGroupBox on focusBenjamin Poulain2009-07-081-5/+1
| | | | | | | | | | | | | | | | We cannot assume the position of the decorations when a QGroupBox get the focus. Task-number: 257660 Reviewed-by: Thierry
| * Document limitation in Cocoa cursor handling.Norwegian Rock Cat2009-07-071-0/+5
| | | | | | | | | | | | | | | | | | | | It seems there is a bug in AppKit which will automatically reset a cursor even when it is grabbed, but won't reset it when it's brought back into the window. The upshot of this is that doing a setCursor() inside of mouse handling behaves slightly different than on the other platforms (including Carbon). However, we are at the mercy of Cocoa here and I would rather have all the other things AppKit does right and live with this bug which they may fix some day.
| * Fix typo in color calculation.Norwegian Rock Cat2009-07-071-3/+3
| | | | | | | | | | | | | | | | | | Argh! It's divide by 256 not 265. The worst part was that I used the same values in Cocoa as well, so they were both "damaged." It should be good now. Task-number: 257499 Reviewed-by: Prasanth Ullattil
| * Fix issue where a mainwindow would show two size grips in Cocoa.Norwegian Rock Cat2009-07-061-2/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | OK. this is a bit strange. It seems the topdata->resizer value is used to control whether or not we should show a resize handle based on a count (0 no, non-zero yes). Since we somehow decided that this value will never be larger than 15, we made it 4-bits wide. There's a "Qt/Mac" API, QWidgetPrivate::qt_mac_update_sizer(QWidget *, int = 0) which would adjust this value by the int passed in.. We use that in several places, not excluding the QStatusBar where we would pass 1 if we want to show, and -1 if we didn't. Now if you subtract -1 from zero when you are 4 bits wide, well, bad things happen. Therefore protect that (since if it's at zero we have succeeded, we don't want to show the resizer). This seems to work well. The private API is certainly an interesting way of solving the problem, but is easy to abuse (for example, this code will break if resizer = 1 and we are passed -2 in the function. Task-number: 257485 Reviewed-by: Prasanth Ullattil
| * Implement QApplication::setOverrideCursor to use pure Cocoa callsNorwegian Rock Cat2009-07-061-1/+11
| | | | | | | | | | | | | | | | | | | | | | Seems this was a victim of our cursor fixing. Cocoa does a lot for us with setting cursors. This meant that we didn't need to do as much meddling and as a result qt_mac_set_cursor does nothing in Cocoa. Unfortunately, this broke setOverrideCursor. Luckily Cocoa has a stack that works exactly like Qt, so we can just use that. Task-number: 257507 Reviewed-by: Prasanth Ullattil
| * Remove unused function viewUnderTransparentForMouseView in QCocoaView.Prasanth Ullattil2009-07-022-57/+0
| | | | | | | | | | | | | | After we implemented hitTest for QCocoaView, this function is no longer used. Reviewed-by: Norwegian Rock Cat
| * Drag and drop events are not delivered correctly in CocoaPrasanth Ullattil2009-07-022-8/+43
| | | | | | | | | | | | | | | | | | | | | | Drag and drop events should consider the WA_TransparentForMouseEvents attribute like the mouse events. If this attribute is set for a widget, the event has to be passed to right widget under mouse. The widget is identified by calling hitTest. In such cases the leave event has to be delivered to the widget which actually accepted the enter event. Task-number: 252088 Reviewed-by: Norwegian Rock Cat
| * Implement hitTestNorwegian Rock Cat2009-07-022-54/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Cocoa calls hitTest on our view to determine if the view should get the mouse press. We always said, "yes" and did all the logic ourselves. Turns out that we can say "no" if I'm transparent to mouse events and remove all that code where we do all the work ourselves. Big maintenance win! For the time being I've kept the "transparentViewForEvent" method since it might be useful for others, but no one is using it at the moment and we may just kill it soon. HitTest should handle this situation correctly.
| * Fix a regression where dynamic tooltips wouldn't show up in Cocoa.Norwegian Rock Cat2009-07-022-4/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Tracking of mouse events was only enabled when enableMouseTracking or Hover or a tooltip had been set explictly on the item, but this meant that the dynamic QEvent::Tooltips would never get dispatched. So, in order to help out people that might use this feature, all QCocoaViews must pay the mouse move event tax *sigh*. I added comments in the proper places so that we DO the right thing for a release where we can force the change in behavior. Task-number: 257320 Reviewed-by: Denis
* | Fix possible crash in QDockAreasThierry Bastian2009-07-081-1/+1
| |
* | Define M_PI in qmath.h if not defined by math.h (as is the case on Windows), ↵Volker Hilsheimer2009-07-082-8/+0
| | | | | | | | and remove duplicate defines elsewhere.
* | QMainWindow: fix the use of animation and improve code qualityThierry Bastian2009-07-083-52/+38
| |
* | QMenuBar: the extension could be visible when it shouldn'tThierry Bastian2009-07-081-2/+2
| | | | | | | | | | If you had invisible actions in the menubar, it would always show the extension button
* | Cocoa: Plain text from clipboard use '\r' as newline instead of '\n'Prasanth Ullattil2009-07-083-2/+25
| | | | | | | | | | | | | | | | | | The 'public.utf16-plain-text' clipboard type maps newlines to '\r' instead of '\n'. The NSStringPboardType from NSPasteboard does this correctly, so first try to get data through this type. Task-number: 257661 Reviewed-by: Norwegian Rock Cat
* | Animations: fix compilation with QT_NO_ANIMATIONThierry Bastian2009-07-084-2/+37
| |
* | QMainWindow: compile fix when defining QT_NO_DOCKWIDGETThierry Bastian2009-07-081-2/+1
| |
* | QMainWindow: fixed a crash in some cases when deleting the widgetThierry Bastian2009-07-082-13/+6
| | | | | | | | | | | | | | | | This happened because the rubberband used as a gapindicator was not allocated on the heap and might have been deleted by the QMainWindow destructor. Task-number: 257626
* | QMainWindow: made use of QPropertyAnimation for animationsThierry Bastian2009-07-084-149/+59
| | | | | | | | This required some refactoring as well. Now code is leaner and cleaner
* | The offset of cropRect should not depend on the position of the windowBenjamin Poulain2009-07-081-1/+1
| | | | | | | | | | The rect cropRect should be positioned with the offset to the top-level window, not the screen position.
* | On Mac OS X, translate the wrect to the coordinates on screenBenjamin Poulain2009-07-071-7/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In the following configuration, wrect was off-screen and the widget was not painted: -scroll area "A" -contains another scrollarea "B" with 2*WRECT_MAX < size < XCOORD_MAX -the widget contained in B has size > XCOORD_MAX -A is scrolled to the the bottom To fix the issue, wrect is moved to the area where the top level window is in the widget coordinate. Task-number: 144779 Reviewed-by: nrc
* | ItemViews: _q_fetchMore now uses a timer instead of invokeMethodThierry Bastian2009-07-073-6/+9
| |
* | Fixes a crash when scrolling a scrollarea with a mouse wheel.Denis Dzyubenko2009-07-072-0/+2
| | | | | | | | | | | | | | | | | | This fixes a crashed introduced in 60e965fd35037f4a27816d2aeccafdff0d6ae9d6 - those lines were removed by accident. Reviewed-by: João Abecasis Author: João Abecasis
* | QColumnView: new uses QPropertyAnimation over QTimeLineThierry Bastian2009-07-072-22/+9
| |
* | Getting rid of compiler warnings on windowsThierry Bastian2009-07-073-9/+5
| |
* | QColumnView: didn't react to addition of rows/cols in the current viewThierry Bastian2009-07-078-21/+61
| | | | | | | | Task-number: 246999
* | Merge branch 'master' of git@scm.dev.nokia.troll.no:qt/qtDavid Boddie2009-07-07159-4126/+6122
|\ \ | | | | | | | | | | | | Conflicts: src/network/socket/qlocalsocket.cpp
| * | QMainWindow: layout private API cleanupThierry Bastian2009-07-072-35/+35
| | | | | | | | | | | | using const references to pass parameter
| * | Make sure we send a ValueChanged event if the spinbox value has changedJan-Arve Sæther2009-07-071-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | Unfortunately the codepath for keyPressEvent does not call updateState, so we have to add the same line in two places. Note that updateState() is only called from mousePressEvent() and mouseMoveEvent(). Task-number: 254053
| * | ItemViews: it would go into DraggingState even without clicking an itemThierry Bastian2009-07-071-1/+1
| | | | | | | | | | | | | | | | | | | | | We now just make sure that we start the drag if there was a pressed index. Task-number: 252643
| * | QMenu: with tearoff handle, it would reserve the space for it twiceThierry Bastian2009-07-071-8/+5
| | | | | | | | | | | | sizeHint is now fixed
| * | QToolBar: better management of positions when hiding/unhidingThierry Bastian2009-07-071-11/+5
| | | | | | | | | | | | | | | | | | | | | The toolbar that one would unhide could be packed at the right of the screen. This was because the last toolbar always has a size that fills the space. So if you unhide a toolbar situated after this one, it got "compressed".
| * | QFontComboBox: used to emit currentFontChanged twice when setting it.Thierry Bastian2009-07-071-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Setting the current font would change the current font and then it would try to select the right model index and get the font only from the text of the combobox. This was resetting the point size of the font, resulting in emitting the signal a second time. In the case of the user, it was also causing signals to be called in a loop. Task-number: 229731
| * | QMenu: the scroller now takes the qapp's global strut into accountThierry Bastian2009-07-062-25/+25
| | | | | | | | | | | | Task-number: 257118
| * | QMenu: scrolling in menus was brokenThierry Bastian2009-07-062-16/+24
| | |
| * | doc: Included note about the effect of WA_NoMousePropagation.Martin Smith2009-07-061-0/+4
| | | | | | | | | | | | Task-number: 162945
| * | QHeaderView::sizeHint: small bug fix and refactorThierry Bastian2009-07-061-5/+5
| | |
| * | Fix to paint big widgets in a scroll areaBenjamin Poulain2009-07-061-5/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If a big widget is inside a scroll area, and this widget is in the limits of XCOORD_MAX, its child might not be inside the limits. The child is then limited to wrect, but wrect might not be on the screen because the parent is scrolled. To avoid this problem, the widgets position should not influence whether wrect is used or not. Task-number: 144779 Reviewed-by: nrc
| * | doc: Added not about Mac OS X.Martin Smith2009-07-061-0/+7
| | | | | | | | | | | | | | | | | | | | | On Mac OS X, QMenuBar::clear() does not remove menu items that have been merged into the system menu bar. Task-number: 255222
| * | doc: Removed specific reference to Mac OS X.Martin Smith2009-07-061-15/+20
| | | | | | | | | | | | Task-number: 256452
generated by cgit v0.12 at 2025-01-23 17:20:57 (GMT)