Hi,
I've seen a few examples where people are cleaning up includes in header
(public or private but exported to other modules) files, as e.g.
http://codereview.qt-project.org/#change,18095.
While they are correct in theory, they cause problems in practice and
provide close to 0 (in fact
Wouldn't PointerArea make a bit more sense. MS have also introduced MSPointer
in IE10[1] which represents a mouse, finger-touch or stylus.
[1]
http://blogs.msdn.com/b/ie/archive/2011/09/20/touch-input-for-ie10-and-metro-style-apps.aspx
Kenneth
From:
On Thu, 1 Mar 2012 18:26:28 ext Samuel Rødal wrote:
On 02/29/2012 05:20 PM, ext Shawn Rutledge wrote:
The proposal is this: I think we need to have a QML PointingArea element
which looks just like MouseArea except that it handles both mouse events
and single-touch events the same way. Then
On quinta-feira, 1 de março de 2012 08.22.42, lars.kn...@nokia.com wrote:
Hi,
I've seen a few examples where people are cleaning up includes in header
(public or private but exported to other modules) files, as e.g.
http://codereview.qt-project.org/#change,18095.
While they are correct in
On 3/1/12 11:02 AM, ext Thiago Macieira thiago.macie...@intel.com
wrote:
On quinta-feira, 1 de março de 2012 08.22.42, lars.kn...@nokia.com wrote:
Hi,
I've seen a few examples where people are cleaning up includes in header
(public or private but exported to other modules) files, as e.g.
Am Donnerstag, den 01.03.2012, 11:27 + schrieb lars.kn...@nokia.com:
On 3/1/12 11:02 AM, ext Thiago Macieira thiago.macie...@intel.com
wrote:
On quinta-feira, 1 de março de 2012 08.22.42, lars.kn...@nokia.com wrote:
Hi,
I've seen a few examples where people are cleaning up includes
On 1 March 2012 10:09, kenneth.r.christian...@nokia.com wrote:
Wouldn't PointerArea make a bit more sense. MS have also introduced MSPointer
in IE10[1] which represents a mouse, finger-touch or stylus.
[1]
On quinta-feira, 1 de março de 2012 12.44.47, Mathias Hasselmann wrote:
According to the book it is. But in practice it happens all the time, and
we know it.
To which book? C++ compilers and IDEs give zero support in enforcing
direct includes. Considering the mess GNU libc headers are, I
Torsdag 1. mars 2012 19.48.15 skrev ext Alan Alpert:
On Thu, 1 Mar 2012 18:26:28 ext Samuel Rødal wrote:
On 02/29/2012 05:20 PM, ext Shawn Rutledge wrote:
The proposal is this: I think we need to have a QML PointingArea element
which looks just like MouseArea except that it handles both
On 03/01/2012 02:49 PM, ext Frederik Gladhorn wrote:
Torsdag 1. mars 2012 19.48.15 skrev ext Alan Alpert:
On Thu, 1 Mar 2012 18:26:28 ext Samuel Rødal wrote:
On 02/29/2012 05:20 PM, ext Shawn Rutledge wrote:
The proposal is this: I think we need to have a QML PointingArea element
which looks
On 1 March 2012 15:16, Samuel Rødal samuel.ro...@nokia.com wrote:
It's possible to make MouseArea a sub-class of whatever we actually want
to call it, and mark it as deprecated. That way it could be removed down
the line, or made to only handle the MouseEvent type. Similarly we could
have a
Hi,
If you want to mentor a project or if you have a proposal to make, please
sign up at http://wiki.qt-project.org/GSOC_Proposals.
Although there hasn't been much discussion, I'm happy to see that some
proposals are being made :-)
Just for the records: some ancient proposals from some year
Shawn:
BTW back in the 80's I knew an old civil engineer who was new to
computers (more of a slide-rule guy) and thought that mouse referred
to what we usually call the cursor (the arrow on the screen). I've
also seen in the context of CAD digitizing tablets that the puck you
move around on
From: Olivier Goffart oliv...@woboq.com
On Thursday 01 March 2012 12:44:47 Mathias Hasselmann wrote:
Sadly, considering the slowness of g++ and the complexity of Qt, I doubt
this is a reasonable approach for Qt.
That's what pre-compiled header are for.
Not everyone uses pre-compiled headers,
14 matches
Mail list logo
