| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Reviewed-by: Trust Me
Inspired-by: Olivier Goffart's earlier change
Pain-by: Git
|
|
|
|
| |
Reviewed-by: Trust Me
|
|
|
|
|
| |
Not a proper fix, but let's see if this increases reliability of the
results.
|
|
|
|
|
|
| |
Wonder how it survived for so long.
Reviewed-by: Peter Hartmann
|
|
|
|
|
|
|
| |
Slightly increase threshold for when to shrink an FBO, and reduce the
number of calls to glBindFramebuffer.
Reviewed-by: Tom
|
|
|
|
|
|
|
|
|
| |
The auto-test was failing because it calculate the scrollbar indent
using style primitives. It's very fragile and doesn't work on MacOS
style (and may not work on other style too). Since we don't test style
stuff here, we can just apply the plastique style for this test.
Reviewed-by:TrustMe
|
|
|
|
|
|
|
|
| |
Use the -MT command line option so it links statically with libc.
The reason for this is that not all windows versions have the DLL
"out of the box".
Reviewed-by: Marius Storm-Olsen
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Reviewed-By: Jason Barron
Reviewed-By: Alessandro Portale
Summary:
QT_NO_CURSOR is now not defined for symbian builds
Existing QCursor APIs are all supported
New public API, QApplication::setNavigationMode, to allow the navigation
mode to be set. I.E. on an S60 3.2 phone, some applications will want a
virtual mouse cursor (web browser), while others are designed for keypad
navigation.
Symbian HAL is used for detecting input capabilities.
Fix DND, code cleanup & comment
QCursor visibility now uses a refcount, and is called from DND and the
setNavigationMode so they are both simpler and don't interfere with each
other.
QApplication::setNavigationMode
New public API for configuring cursor/keypad navi style.
This links in with ongoing work on the 4-way keypad navi branch, but
2-way and 4-way modes both act as 2-way mode until that is integrated
Some of the demos/examples have cursor switched on (those that were not
usable with keypad)
Virtual mouse support for non touch, non mouse phones (tested on N78)
add *.d and .metadata (carbide debug file / workspace dir) to .gitignore
System pointers are unavailable when using sprite workaround, so the
system cursor shapes are compiled into qtgui as resources.
MAC port does this also for shapes that aren't standard on the MAC.
Refactor Drag'n'Drop to use QCursor
Add test case to check all system cursor shapes
Simply a mainwindow containing a label widget for each cursor shape,
with the cursor property set appropriately
QCursor(QBitmap,QBitmap) supported
Fixed problem with the image & mask being inverted when using the
QCursor constructor that takes two mono bitmaps.
add .make.cache files to .gitignore
Correct implementation of QApplication::setOverrideCursor
QApplication::restoreOverrideCursor and QApplication::setOverrideCursor
are now working correctly on Symbian platform.
Performance will be slower compared with other platforms, because the
Symbian window server has a cursor associated with each native window.
Add test case for custom cursors
Create a pixmap cursor and associate it with a widget.
No changes to production code, since test passed 1st time ;)
Add manual test for QCursor
Make cursor independent of construction order
Updated to work around window server issue where contruction order
affects what cursor is displayed in child windows.
Also changed to effectiveWinId following review comments
Also fixed a problem which would make qcursor not link if configured
with QT_NO_CURSOR
Moved some multiply declared extern functions from cpp to _p.h files
Implemented Symbian versions of the cursor functions.
Merged in work I'd done based on tower.
Fill in bits of stub functions based on windows port
Removed QT_NO_CURSOR from list of config options forced on symbian
Recompiled configure.exe
Added stub functions for the missing functions in s60 port
|
|
|
|
|
|
| |
We could sometimes have more than two paint events even before reaching
QTRY_COMPARE, thus it would fail.
The test failed on Windows.
|
|
|
|
|
|
|
|
| |
The bug was triggered by setting focus on a parent scope (which then
passes focus to the innermost scope). Subfocus was set up for the
first scope, but not the inner scopes.
Reviewed-by: TrustMe
|
|
|
|
|
|
|
| |
This came in with change c8bf9bd17a4520eefe4306b7b1bb4f93fb296d80, by
accident - it was a leftover after debugging.
Reviewed-by: Martin Smith
|
|
|
|
| |
Reviewed-by: Peter Hartmann <peter.hartmann@nokia.com>
|
| |
|
|
|
|
|
|
|
|
| |
If the file started with a comment (/* .. */) the parser would not see
the first '/' character, thus it would not treat it as a comment.
This was because we called getChar() just before we called parse(),
and just after we had entered parse().
|
| |
|
|
|
|
|
|
|
|
| |
The GL1 engine will use the raster fall back for pixmap filters. We
anyhow use GLSL for the filters, which requires OpenGL 2 support, and in
that case the GL2 engine is the default.
Reviewed-by: Gunnar Sletta
|
|
|
|
|
|
|
|
| |
receiving the WSAEMSGSIZE error means we could not read all the data
because the buffer was too small, but still we should return the number
of bytes read and not return -1
Reviewed-by: Marius Storm-Olsen
|
|
|
|
| |
Reviewed-by: Paul Olav Tvete
|
|
|
|
|
|
| |
Also fix the relations in the documentation
Reviewed-by: David Boddie
|
| |
|
|
|
|
|
|
|
| |
This greatly increases the blur quality in the OpenGL implementation,
and doesn't affect the performance of the raster implementation.
Reviewed-by: Bjørn Erik Nilsen
|
|
|
|
|
|
| |
Fetch the correct password character from the style.
Reviewed-by: Olivier
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1) Need to transfer to brush drawing mode when switching active engine,
to make sure we reset the vertex / texture coordinate pointers for image
drawing.
2) QGLPixmapGLPaintDevice::beginPaint() was changed to use
QGLContext::drawTexture() for blitting the old texture contents to the
render FBO, which means that we also need to set up viewport, modelview,
and projection matrices, and ensure that clipping / stencil testing
is disabled.
3) Make sure stencil testing is disabled when clearing the FBO.
Reviewed-by: Tom
|
| |
|
|
|
|
|
|
| |
Became unexported from commit bcd23411c8
Task-number: 261250
|
|
|
|
| |
Reviewed-by: Jan-Arve
|
|
|
|
| |
Reviewed-by: Jesper
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This feature is essential for Declarative UI, but does not add much
value for C++ developers. A FocusScope provides a stack of focused
widgets, and it ensures that the topmost item on the stack has
focus if any of the items in the stack gains focus. When the topmost
loses focus, focus is passed to the "parent" focus scope, and so on.
You can get almost the same behavior using panels (ItemIsPanel),
except panels impose other behavior, like stopping clickfocus
propagation, and stopping event propagation in general. In a QML
world you would typically use FocusScope for controlling focus
locally, and panels when you need to maintain separate focus stacks.
Reviewed-by: akennedy
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Make sure you can't set focus on an inactive scene, allow items
with subfocus to gain focus even if added to a scene that's not
active, and finally ensure that activating a panel in an active,
but unfocused scene, gives focus to the scene.
Also added a test that checks adding normal vs. panel items to an
active vs. inactive scene, and what happens if you initially say
the item should have focus.
Reviewed-by: TrustMe
|
|
|
|
|
|
|
|
|
|
|
| |
This line was added to fix crashes when deleting items that had
a subFocusItem pointing to a child that was already deleted. This
bug was fixed by ebb1162f54a29baeccb71d1e283146892629518f. After
this, subFocusItem is always 0 at this point.
The original change was eb3d5a73148cd7206c6b3b6672ed47b44611f745.
Reviewed-by: TrustMe
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The widget must be created before calling QInputContext::setFocusWidget.
Otherwise we run into an assertion. Yes, this only occurs in debug
configuration but its still annoying...
Cherry-pick of commit d6b8f81a2440e7a507ecbb1becd90ef284510787 from master.
Reviewed-by: thartman
Conflicts:
tests/auto/qwidget/tst_qwidget.cpp
|
| |
|
|
|
|
|
|
|
|
|
| |
Bauhaus uses grabMouse to implement their own Drag and Drop mechanism.
Cocoa port never considered the grabber widget. All the mouse events
will now be routed to the mouse grabber widget.
Task-number: 261245
Reviewed-by: MortenS
|
|
|
|
| |
Reviewed-by: Trond
|
|
|
|
| |
Pointed out by Caio.
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The bug appeared only when calling collidingItems right after setPos.
When calling setPos on a parent the sceneTransform is mark as dirty, so
when we paint the parent and its children if the scene transform of the
parent was dirty then we update all children sceneTransform. In our
case here, collidingItems call ensureTransform on one of the children
which go recursively to the top most dirty item and update the
sceneTransform. The problem is that all sibling children are not mark
their sceneTransform dirty so next paint will skip them (since the parent
is not dirty anymore).
Task-number:260711
Reviewed-by:bnilsen
|
|/
|
|
|
| |
Reviewed-by: Samuel
Reviewed-by: Tom Cooksey
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
Uses the primary key from the index in the query, not the resulting
location in the modified dataset.
Task-number: 222678
|
| |
| |
| |
| | |
Reviewed-by: Justin McPherson
|
| |
| |
| |
| |
| |
| | |
There should be no semi-colon after Q_DISABLE_COPY.
Reviewed-By: Trust Me
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Ammend commit 41dbc4406 and 21cf7b4c431742
We do not always get the mouseReleaseEvent (because the popups grabs the
mouse. So set mouseDown to false in the mouseMoveEvent if no buttons are
pressed.
We also need to call setCurrentAction(0) in the case we are hovering on
the empty area with no popup open. (in otder to remove the highlight)
The code is now much closer to the code before the two previous commit
Reviewed-by: Prasanth
|
|\ \
| |/ |
|
| |
| |
| |
| |
| |
| |
| | |
max_keycode wasn't retrieved.
Merge-request: 1308
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@nokia.com>
|
| |
| |
| |
| |
| |
| |
| | |
We have to munmap() what we have mmap()ed
Reviewed-by: Gunnar
Reviewed-by: Jeremy
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This also creates a new header called QtTest/QtTestGui. This header is
not supported. You should #include <QtTest/QtTest>. But if you're
using a build system that is not qmake, QT_GUI_LIB isn't defined, so
it's possibly easier to #include this new header.
Reviewed-by: Trust Me
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This allows #including qtestmouse.h and qtestkeyboard directly to get
mouse testing. All QtTest headers are still unsupported (you should
always include QtTest/QtTest) but we can still fix issues like this.
I have verified with the preprocessor that no GUI code is enabled by
including QtTest if QT_GUI_LIB isn't defined. This should not bring
the MinGW autotest failures back that the a250ca3a3c0 commit was
trying to fix.
Reviewed-by: Trust Me
|
| |
| |
| |
| |
| |
| |
| |
| | |
When a button is pressed, a popup message is shown and the background
(everything, every items, behind the popup message) is faded to light
green.
Reviewed-by: Bjørn Erik Nilsen
|