This is the message I get when I try to access it:
Site Error: Unable to Load Site Preferences; No Preferences Found
Sorry for sending to this list but figured out someone here would know what
to do about it.
Felipe
___
Development mailing list
Develop
Something like PointerArea would be nice to have, but it is not something we
can throw in while in feature freeze. What we have now is a little clunky, but
it works, and has been very well tested and debugged over some years. I don't
want to discourage anyone from working on this, but it's not
> From: Olivier Goffart
>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, nor should
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.
___
Development mailing list
Devel
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 aro
> From: Thiago Macieira
>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. Consider
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
On 1 March 2012 10:48, Alan Alpert wrote:
> The overlapping MouseArea/TouchArea is an interesting idea, and might explain
> why we'd need a TouchArea when it's virtually identical to the 'PointerArea"
> element. But then we'd have three area interaction elements that are virtually
> identical, wit
On 1 March 2012 15:16, Samuel Rødal 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 TouchArea convenience
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
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 handle
Hi,
We are removing some macros from qdoc and replacing them with proper qdoc
commands.
The following are the results:
-We are going to standardize on Doxygen, this means:
-\e will output italic (emphasized) text. In HTML and DITAXML output this will
be , Doxygen outputs for HTML, but DITAXML
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
On 1 March 2012 10:09, 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]
> http://blogs.msdn.com/b/ie/archive/2011/09/20/touch-input-for-ie10-and-metro-style-apps.aspx
I had thought of t
Am Donnerstag, den 01.03.2012, 11:27 + schrieb lars.kn...@nokia.com:
> On 3/1/12 11:02 AM, "ext Thiago Macieira"
> 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
Hi,
> 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
>
That "hardware agnostic" abstraction la
On 3/1/12 11:02 AM, "ext Thiago Macieira"
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.
>> http://coderevi
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 correc
On quinta-feira, 1 de março de 2012 10.32.05, André Somers wrote:
> While I find this dicussion interesting, I am wondering about the
> relation with the Qt 5 feature freeze that has gone by a few weeks ago,
> and Lars' email about that on february 22 ("Important: Qt 5 freeze"). Do
> you think it i
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.
While I find this dicussion interesting, I am wondering about the
relation with the Qt 5 feature freeze that has gone by a few weeks ago,
and Lars' email about that on february 22 ("Important: Qt 5 freeze"). Do
you think it is possible to tackle this in 5.1, or does it need binary
or even sourc
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: d
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 we need to start using it
> instead of MouseArea in a
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 negative)
24 matches
Mail list logo