summaryrefslogtreecommitdiffstats
path: root/src/gui
Commit message (Collapse)AuthorAgeFilesLines
* Added QTextListFormat::ListUpperRoman and QTextListFormat::ListLowerRoman ↵Nils Jeisecke2009-07-139-7/+85
| | | | | | | for roman numbering of lists as supported by HTML/ODF Reviewed-by: Olivier Goffart Merge-request: 681
* QTreeView: now dragging lots of items is fastThierry Bastian2009-07-134-2/+47
|
* Fix font propagation issues with QComboBox and the popup menu.Norwegian Rock Cat2009-07-133-4/+16
| | | | | | | | | | | | | | | This has always been a bit bumpy, the problem is that the popup normally has its own styling from the desktop, plus it's its own top-level and that is normally a boundary for propagation. Of course, people are surprised by this (especially when it works for editable). So, we need to be a bit better propagating the info. Also the QStyleOptionMenuItem has the correct font, but if it's set on a window, by the time it reaches the popup, its resolve mask is very weak, so it will fail to resolve at all. Setting the point size allows the font to have a bit of strength. Task-number: 257486 Reviewed-by: Jens Bache-Wiig
* Cut-off in QGraphicsView not hit if setting a scene rect.Bjørn Erik Nilsen2009-07-131-1/+1
| | | | | | | | | | QGraphicsScene::sceneRect() returns the growingItemsBoundingRect if not a particular scene rect is set; otherwise the sceneRect is returned. This cut-off aims to do less processing when the exposed region covers the entire scene, but it won't get hit in case of a sceneRect because we always check against the growingItemsBoundingRect. Task-number: 257192
* Unified common code in QSyntaxHighlighter::rehighlight() and ↵J-P Nurmi2009-07-131-17/+14
| | | | | | | QSyntaxHighlighter::rehighlightBlock() Merge-request: 379 Reviewed-by: Simon Hausmann <simon.hausmann@nokia.com>
* Added QSyntaxHighlighter::rehighlightBlock(QTextBlock)J-P Nurmi2009-07-132-0/+28
| | | | | Merge-request: 379 Reviewed-by: Simon Hausmann <simon.hausmann@nokia.com>
* Fix crash after "Remove QT_WA and non-Unicode code paths, dropping Win9x and ↵Bjoern Erik Nilsen2009-07-131-1/+2
| | | | | | | | | | | NT support" tst_QGraphicsProxyWidget crashed because the QAlphaWidget tried to access a deleted widget. Before we had the if check, but that was removed with this commit: 55137901. Completely wrong, we must check the widget pointer before using it. Reviewed-by: jbache
* Merge commit 'origin/4.5'Bill King2009-07-132-6/+3
|\ | | | | | | | | | | | | | | Conflicts: src/plugins/kbddrivers/usb/main.cpp tests/auto/qnetworkreply/tst_qnetworkreply.cpp tests/auto/qwidget/tst_qwidget.cpp
| * Fixed a crash with input methodsPierre Rossi2009-07-102-6/+3
| | | | | | | | | | | | | | | | | | The inputContext's focusWidget was not reset when disabling input methods. Thanks to Benjamin P. Task-number: 257832 Reviewed-by: Denis
* | Fixed linking of QtSvg with MSVC.Rohan McGovern2009-07-133-19/+18
| |
* | QListView: small refactoringThierry Bastian2009-07-112-67/+61
| | | | | | | | It is useless to store the vector of modelindex from intersectingSet
* | ItemViews selection: improve performance of QItemSelection::indexesThierry Bastian2009-07-111-12/+23
| | | | | | | | On windows it makes it 2x faster
* | build fix on windowsThierry Bastian2009-07-111-0/+1
| |
* | ItemViews: make dragging faster when lots of items are selectedThierry Bastian2009-07-114-11/+55
| | | | | | | | | | | | | | QListView know exactly what they have on their viewport and we only paint items clipped to the viewport. So we don't need to ask for each item its visualRect. NB: QTreeView and QTableView probably deservee the same treatment
* | Merge commit 'qt/master' into graphicssceneindexBjørn Erik Nilsen2009-07-10130-4194/+2093
|\ \ | | | | | | | | | | | | | | | | | | Conflicts: src/gui/graphicsview/qgraphicsitem_p.h tests/auto/qgraphicsproxywidget/tst_qgraphicsproxywidget.cpp tests/auto/qgraphicsview/tst_qgraphicsview.cpp
| * | QListView: improve performance on QListView::selectedIndexesThierry Bastian2009-07-101-7/+9
| | | | | | | | | | | | Task-number: 233342
| * | Fix compilation on SnowLeopardNorwegian Rock Cat2009-07-102-5/+5
| | | | | | | | | | | | | | | | | | On 64-bit an id (void *) is 64-bit also, so, it really should be a pointer, but I'll make it a 64-bit int for the time being just so stuff compiles.
| * | ItemViews: make the pixmap from drag and drop more efficientThierry Bastian2009-07-102-14/+21
| | | | | | | | | | | | | | | | | | | | | We don't need to draw all the items that are selected. We just need those whose rect intersects the one from the viewport. Task-number: 233342
| * | Tablet events get delivered to the widget where the tablet down happend.Luc Devallonne2009-07-101-2/+27
| | | | | | | | | | | | | | | | | | | | | | | | This is basically the Windows version of the bug fixed in change 82e825ed841bce324a6892fcbace03f9936d4f4f Merge-request: 855 Reviewed-by: Norwegian Rock Cat <qt-info@nokia.com>
| * | QTableView: auto-scrolling could be broken by invisible sectionsThierry Bastian2009-07-101-2/+2
| | | | | | | | | | | | Task-number: 248688
| * | QTableView: horizontal scrollbar could be inoperent with big columnsThierry Bastian2009-07-101-0/+4
| | | | | | | | | | | | Task-number: 240266
| * | QMainWindow: it is useless to apply the stte after a call to plugThierry Bastian2009-07-101-5/+0
| | | | | | | | | | | | The layoutState is already current (ie. already applied).
| * | QFileDialog: the side urls are now always cleaned when they are localThierry Bastian2009-07-101-4/+9
| | | | | | | | | | | | Task-number: 257579
| * | QDoubleSpinBox: make sure people can't choose too many decimalsThierry Bastian2009-07-101-3/+4
| | | | | | | | | | | | | | | | | | Maximum number of decimals is DBL_MAX_10_EXP + DBL_DIG Task-number: 257291
| * | Support Tablet coordinate on Windows with non-zero physical originLuc Devallonne2009-07-102-13/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Most Wacom tablet have a coordinate origin at 0 (Bamboo,Intous), but some tablet (like DTF 720, which have an integrated screen) have a non zero coordinate origin. Which lead to an errounous y/a tablet pos reported by Qt tablet event. Merge-request: 822 Reviewed-by: Norwegian Rock Cat <qt-info@nokia.com>
| * | Ensure that when we hide QToolBar in unified, unified follows.Norwegian Rock Cat2009-07-0910-42/+161
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Basically if you would hide a toolbar in the unified toolbar, you would still see a little bit of area at the top instead of having everything flush with the titlebar. This change basically unsures that the unified toolbar makes a decision to hide itself if all the toolbars inside it are hidden. It makes the behavior of clicking on the toolbar button behave more or less correctly since we are going to show the unified toolbar whether we want to or not. This all will get the toolbar button switch event to be dispatched in Cocoa as well. Also add an optimization for checking if we need to change the geometry. If we don't have any items the other toolbar areas, we can skip the set geometry call, which wrecks havoc with things in Cocoa. We still don't solve the case of someone who has hidden the items with the toolbar button then goes full-screen, then goes back out. I'm not motivated to solve it as is because we need to keep track of the hides we do on the button press vs. other hides from the user and still people can workaround it easy enough by handling window state change and doing what is recommended in the docs. Task-number: 208439 Rev-by: Denis
| * | 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
generated by cgit v0.12 at 2024-11-15 20:11:15 (GMT)