| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Know Qt Designer document.
Task-number: 165435
Reviewed-by: Friedemann Kleint <friedemann.kleint@nokia.com>
|
|
|
|
|
|
|
| |
Added a comment about the use of negative indexes.
Task-number: 249344
Rev-by: Marius Storm-Olsen
|
|
|
|
|
|
|
|
|
| |
QSortFilterProxyModel::indexFomSource and *ToSource
Show a warning instead
Task-number: 252507
Reviewed-by: Marius Bugge Monsen
|
| |
|
|
|
|
|
|
|
|
| |
export QWS_DISPLAY=directfb:boundingrectflip to enable calling Flip on
the bounding rect of the dirtied area rather than each dirty rectangle.
This could be faster if you update many small rectangles.
Reviewed-by: TrustMe
|
|
|
|
|
|
| |
Qt's coding style => Object *ptr, not Object* ptr
Reviewed-by: TrustMe
|
|
|
|
|
|
|
| |
Print out detailed information about acceleration mask, blitting flags
and drawing flags when passing debug.
Reviewed-by: Donald <qt-info@nokia.com>
|
|
|
|
|
|
|
| |
Clean up code and make it possible to set more DFBSurfaceCapabilities on
the primary surface.
Also allow users to force systemonly for the surfaces.
|
|
|
|
|
|
|
|
| |
Since I am taking a copy of the description anyway it makes sense to
just pass this light-weight object in as a copy rather than a const
pointer.
Reviewed-by: Donald <qt-info@nokia.com>
|
|
|
|
| |
Reviewed-by: Donald <qt-info@nokia.com>
|
|
|
|
|
|
|
| |
d->clip() might return 0 at this point so make sure we check before
accessing it.
Reviewed-by: TrustMe
|
|
|
|
| |
Best as I can determine via trial and error. It should make vc6 compile again though.
|
|
|
|
|
|
|
|
|
|
| |
According to the (old) cookie RFC 2109, the domain attribute must
always contain a leading dot. Some servers do not have that, but all
browsers accept those cookies anyway, so we should do that as well.
Reviewed-by: Olivier
Reviewed-by: Denis
Task-number: 228974
|
|
|
|
|
|
|
|
|
| |
This autotest tests some Windows Mobile 5.0 specific thing like the
native menubar and the integration into the window manager by taking and
comparing screenshots. This should prevent nasty regressions we had.
This autotest makes only sense on Windows Mobile 5.0 in 480x640
Reviewed-by: maurice
|
|
|
|
| |
Missed a whitespace - corrected it. No task
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For a progress bar with a style sheet applied to it, this
fix ensures that the timer event is passed to the event
handler that updates the busy indicator animation state.
Essentially, the bug was that the decision that the
event was processed by the proxy style object (baseStyle())
was based only on the return value from the event() function.
In this case it is necessary to check that the event was
accepted as well.
Reviewed-by: ogoffart
Reviewed-by: brad
Task-number: 252283
|
|
|
|
|
|
|
| |
current item on show
Task-number: 252534
Reviewed-by: ogoffart
|
|
|
|
|
|
|
|
|
|
|
| |
QApplication::setStyle() caused a crash if called before
constructing the QApplication instance for custom styles. The reason
was that polish tried to create a pixmap (which is not allowed before
qApp is running). This fix checks that qApp exists. Polish will anyway
be called again when qApp gets constructed.
Task-number: 243697
Reviewed-by: Bjørn Erik Nilsen
|
|
|
|
| |
We only want to dump images *if* RENDER_DEBUG is defined.
|
|
|
|
|
|
| |
Avoid QRegion<->QPainterPath conversion if possible.
Reviewed-by: Samuel
|
|
|
|
|
|
|
|
|
| |
We can speed up the calculation by using rect intersections
if possible, i.e. QRegion &= QRect instead of QRegion &= QRegion.
Then we'll get rid of one QRegion construction and the intersection
itself is slightly faster.
Reviewed-by: Samuel
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The problem was that we didn't take the painter's clip into account
when setting the system viewport ("hard clip"). We only used the system
clip, but we have to use system clip + painter clip, which is the
current engine clip. Unfortunately, we have to calculate it again
since there's no cross-platform way of retrieving it.
This was only a problem with Qt::(Replace|No)Clip, since we
in all other cases combine the old clip with the new one.
(Uber cool) auto test included.
Task-number: 250482
Reviewed-by: Samuel
|
|
|
|
|
|
|
|
| |
Wrote documentation for the flowlayout class.
Task-number: 252548
Rev-by: Geir Vattekar
Rev-by: janarve
|
|
|
|
|
|
|
| |
Corrected bugs in the example and added markers for snippets in the documentation.
Task-number: 250616
Rev-by: Geir Vattekar
|
|
|
|
|
|
| |
Changed smae to same
Taks number:251646
|
|
|
|
|
|
|
| |
An item is not deleted when removed from the index. The remaining items get a new index. I changed deleted to removed.
Tasknumber: 252547
Rev-by: janarve
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Addendum to change 9b674ddcea7c0ff7912f185474b7d98bc83bd39f.
The problem was that QWidget::paintEngine() (pure virtual) was
called while being in the destructor. The use-case itself
(see above change) is very very corner case, but still,
it shouldn't crash.
Reviewed-by: bnilsen
|
| |
| |
| |
| |
| | |
Task-number: Related to 241466
Reviewed-by: Samuel
|
| |\ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Don't setfault when setting 0 for the network cache such as when you
want to disable it.
Reviewed-by: Peter Hartmann
|
| | |
| | |
| | |
| | | |
It seems that after approx version 2.7.0, microsoft changed the ODBC types of certain functions, to cater for 64bit architectures. This tries to be a little bit smarter about which types are used in which places.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Alleviates the performance hit of querying the database except when necessary,
try and use XSQLVAR as much as possible, except for floating point fields.
Task-number: 252426
|
| |/
| |
| |
| | |
Reviewed-by: Trust Me
|
| |\ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Make code more readable by not chaining to QScreenCursor for hide/show.
Since hwaccel is true we don't need the exposeRegion call anyway.
Reviewed-by: TrustMe
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The enabling/disabling of the Cursor belongs in the
QDirectFBMouseHandler class and not in the QDirectFBScreenCursor. Even
if we use the Qt software cursor we need the events to come in from the
mouse handler.
Reviewed-by: TrustMe
|
| |/
| |
| |
| |
| |
| | |
No need to be excessively clever here.
Reviewed-by: Trust Me
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Refactor cursor management code to do. No need to change the cooperative
level four times for each show/hide. Simplify code a little.
Also we used to disable the cursor when we wanted to hide it which meant
that we no longer received mouse events.
Reviewed-by: Donald <qt-info@nokia.com>
|
| |
| |
| |
| |
| |
| |
| | |
Instead of having multiple bool QDirectFBScreen::.* getters I added
DirectFBFlags QDirectFBScreen::directFBFlags() function.
Reviewed-by: TrustMe
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is currently the only way I can make QGraphicsView not have to fall
back to the raster engine for all operations. It seems the QRegion
passed to the paintEvent of QGraphicsView also is set as the systemClip
which in the end makes the QRasterPaintEngine's clipRegion equal the
systemClip. By exporting QWS_DISPLAY=directfb:ignoresystemclip you can
now draw without having a complex clip and therefore take advantage of
hw acceleration with DirectFB.
Reviewed-By: Donald <qt-info@nokia.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Allow programmers to select which operations they want to warn
on/disable and which not to.
To warn for DRAW_PIXMAP only you can do this:
DEFINES += QT_DIRECTFB_WARN_ON_RASTERFALLBACKS=DRAW_PIXMAP
To include fillRect you can do:
DEFINES += \"QT_DIRECTFB_WARN_ON_RASTERFALLBACKS=DRAW_PIXMAP|FILL_RECT\"
Reviewed-by: Donald <qt-info@nokia.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
All these drawing functions really shouldn't be const even if some of
them can be. They should never be called from const functions and
when/if they change pen/brush stuff they cease being able to be const.
Also make sure fillRegion() uses the right brush.
Reviewed-by: Donald <qt-info@nokia.com>
|
| |
| |
| |
| |
| |
| | |
It basically says that on KDE and GNOME the native dialogs are called.
It fix a mistake about a regular instantiation on QFileDialog object
on Windows.
|
| |
| |
| |
| |
| |
| | |
version from a Linux machine.
Reviewed-by: trustme
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
and QSelectionModel::columnsIntersectsSelection
The documentation says "if one is selected" inside the row/column, so we
need to look over if we find one which is selected
Task-number: 252069
Reviewed-by: Marius Bugge Monsen
|
| |
| |
| |
| |
| |
| |
| |
| | |
Argh! Copy and paste is evil, not only was the test was wrong, We sent
the event twice and the second time we sent the wrong value.
Task-number: 250668
Reviewed-by: Morten Sørvig
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The test fails because, in cocoa, when resizing a window to zero (either
w or h), cocoa will also move the window up in the corner (!). So the
fix is to issue an extra move back to it's true location after the
resize. The faulty cocoa move is issued inside the resize callback, so
we choose to not update the window location anymore from a pure resize
callback.
Task-number: 251895
Reviewed-by: Trenton Schulz
|
| |
| |
| |
| |
| |
| |
| | |
We always called QStringList::split in this function, which was
just expensive.
Reviewed-by: mauricek
|
| |
| |
| |
| |
| |
| |
| |
| | |
On small screens use the whole screen width when adjusting the size of
the messagebox.
Task-number: 251925
Reviewed-by: Brad
|