| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
src/3rdparty/webkit/VERSION
src/3rdparty/webkit/WebCore/ChangeLog
src/3rdparty/webkit/WebKit/qt/ChangeLog
tests/auto/qgraphicsitem/tst_qgraphicsitem.cpp
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
After discussing with some of the Objective-C
people I have finally got a fair number of the
warnings to disappear in both 10.5 and 10.6. I
also took the opportunity to remove a bunch of
other warnings.
Reviewed by: Morten Sørvig
|
| | |
|
| |
| |
| |
| | |
Task-number: 212058
|
| |
| |
| |
| | |
Task-number: 256287
|
| |
| |
| |
| |
| |
| | |
button and still be able to activate an action
Task-number: 253494
|
| |
| |
| |
| | |
Reviewed-by: Samuel
|
| |
| |
| |
| |
| |
| |
| |
| | |
An item without menu could stay highlighted even when the mouse left
the menu bar.
Task-number: 256322
Reviewed-by: alexis
|
|\ \
| |/ |
|
| |
| |
| |
| | |
Reviewed-by: Trust Me
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When typing directly text cursor is always visible (and if it isn't,
the widget automatically scrolls to make it visible). It should work
the same when typing using input methods.
Task-number: 254766
Reviewed-by: trustme
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Hide duplicate separators and separators at the beginning and end of the
menu. The main challenge here is that separators and "normal" menu items
can be added in any order, for example add all the separators first
and then fill in the items. This means that we have to redo the visibility
decision for separators above and below when adding normal items.
Reviewed-by: Prasanth Ullattil
|
| |
| |
| |
| |
| | |
Width 0 was used as magic value to optimize the widget's startup and initial resize. We
now use the illegal value -1 as magic value insetad.
|
| | |
|
| |
| |
| |
| |
| | |
Removed calls to the widget getters because we have the members directly
in the private class.
|
| |
| |
| |
| | |
we get a "sticky" effect
|
| | |
|
| | |
|
| |
| |
| |
| | |
private class member.
|
| |
| |
| |
| |
| | |
Task-number: 250147
Reviewed-by: Thierry
|
| |
| |
| |
| | |
it uses les foreach
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
What could happen starting with 4.4 is that you could move a toolbar.
If you then added actions, the toolbar would grom and make the other
toolbars move to the right although it had enough space already to show
the newly created actions.
Autotest will follow shortly.
Task-number: 226060
|
| |
| |
| |
| |
| |
| |
| | |
seem fixable easily)
Merge-request: 594
Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com>
|
|\ \
| |/ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
No progress bars on the mac show text and it would be bad if we allowed
it. There's nothing stopping people from connecting the valueChanged()
signal to a slot and have a real label layed out correctly that actually
updates with the amount of time it takes to complete, etc. This is more
what they do on Mac OS X if they decide to show a label.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This was quite a bug and it showed to some issues that I hadn't taken
into account when doing the initial port to Cocoa. The issue was that we
weren't "merging" items into the application menu if an item had already
been associated with it. Which seems OK for applications that create one
window with one menubar, but breaks down horrible when you have multiple
windows with each having their own menubar. The result is that items in
the application menu potentially go to the wrong window (and the
potential crash). Since there can only ever be one "Quit", "About", or
"Preferences" menu item in Cocoa, we need to make sure that we keep
these items in sync whenever we switch the menubar or remove actions
that are being deleted. That's what we do here.
FWIW, QActions with "ApplicationSpecificRole" for their menu role have
potential to cause memory leaks or other bugs if abused. If you are a
happy open source hacker who wants a thankless job, solving them would
get you lots of goodwill in my book.
Task-number: 255038
Reviewed-by: Richard Moe Gustavsen
|
| |
| |
| |
| |
| |
| |
| | |
a QStatusBar
Task-number: 253717
Reviewed-by: ogoffart
|
| |
| |
| |
| |
| | |
These function exist for making code not look so crazy, so let's
actually use that in code where it didn't exist before.
|
| |
| |
| |
| |
| |
| |
| | |
but the current highlighted item doesn't change
Task-number: 254238
Reviewed-by: ogoffart
|
| | |
|
| |
| |
| |
| |
| |
| | |
Argh! This was a private function and I assumed that I had the boolean
correct, but I was wrong. Anyway, we don't need to do the group fade be
default ever, so always have it false.
|
| |
| |
| |
| |
| |
| |
| | |
Could be caused by change d2cba538
Reviewed-by: jbache
Task-number: 254083
|
| |
| |
| |
| |
| |
| |
| |
| | |
We need to check all window anchestors of the sheet to make sure
that there it is not in effekt application modal
Task-number: 254543
Reviewed-by: Trenton Schulz
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
On Mac OS X, when you have a large hierarchies of menus and you select
the item at the end of the hierarchy. It will flash and then the rest
will fade out at the same time. Qt would do a phased approach which was
what no one expected. Introduce a QMacWindowFader class that can hold an
arbitrary number of qwidgets and then on command fade them all down
pased on the set duration. The API is a bit clumsy but is prefect for
this internal API.
Task-#: 251700
Reviewed-by: Richard Moe Gustavsen
|
| |
| |
| |
| |
| | |
Reviewed-by: Olivier Goffart
Request-url: http://qt.gitorious.org/qt/qt/merge_requests/382
|
| |
| |
| |
| |
| | |
used character operations whenever possible
better usage of QLatin1String
|
| |
| |
| |
| |
| |
| |
| | |
Also fix an issue in QTreeView where a signal could be connected
several times
Reviewed-by: Thierry
|
|\ \
| |/
| |
| |
| | |
Conflicts:
tests/auto/qtreeview/tst_qtreeview.cpp
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
On XP and Vista where tabs use taboverlap, the currently
dragged would loose the outline. We need to compensate for the
taboverlap when creating the draggable widget, otherwise the
outline will be clipped.
Task-number: 254453
Reviewed-by: nrc
|
| |
| |
| |
| |
| |
| | |
olsFrameStyle was old.
Reviewed-by: jbache
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We had a report from a customer saying this breaks if the decimal
separator is the same as the group separator. This is not really
something we want to support, but because this fix is easy and cleanup
the code I decided to fix it.
Reviewed-by: Thierry
Task-number: 253962
|
| |
| |
| |
| |
| |
| |
| | |
Wherever I found that we were using a string instead of a single char
I fixed the code.
Reviewed-by: olivier
|
|\ \
| |/ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Regression from 4.4 introduced while fixing task 167106
Autotest: tst_QComboBox::task253944_itemDelegateIsReset()
Task-number: 253944
Reviewed-by: jbache
|
|\ \
| |/ |
|
| |
| |
| |
| |
| | |
Signed-off-by: Andre Haupt <andre@bitwigglers.org>
Reviewed-By: Thiago Macieira
|
| |
| |
| |
| |
| |
| | |
Usually, "the the" is not proper English
Reviewed-By: Thiago Macieira
|
|\ \
| |/
| |
| |
| |
| |
| | |
Conflicts:
src/corelib/kernel/qobject.cpp
src/corelib/kernel/qobject_p.h
src/network/access/qhttpnetworkconnection.cpp
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
According to the documentation, QCalendarWidget::setDateTextFormat() should
reset the format if the date is not valid.
New tests included for the formating of this widget.
Task-number: 252943
Reviewed-by: Olivier
|