On sexta-feira, 12 de outubro de 2012 07.27.51, Marc Mutz wrote:
Hi,
I was wondering whether we should stop using the pattern of declaring
_q_privateSlots() in favour of connecting to functors or functions directly.
Makes sense, except that it's of inconvenient use:
- lambdas: can't use in
Since no one has spoken up, that means we have the official Qt 5.0 release list.
It will include the following Git repositories:
qtbase
qtwebkit
qtquick1
qtdeclarative
qttools
qtwebkit
qtactiveqt
qtmultimedia
qtimageformats
Hi,
Lars mentioned in Digia acquisition closed mail a while ago that we need to
change the copyright headers in all Qt source files from Nokia to Digia.
AFAIK: Iikka did that work for master branch in all Qt5 repositories. However
in some of the Qt5 repositories there are other branches as
On Thursday 11 October 2012 23:06:18 Thiago Macieira wrote:
On sexta-feira, 12 de outubro de 2012 07.27.51, Marc Mutz wrote:
Hi,
I was wondering whether we should stop using the pattern of declaring
_q_privateSlots() in favour of connecting to functors or functions
directly.
Makes
On Friday October 12 2012, Thiago Macieira wrote:
On sexta-feira, 12 de outubro de 2012 07.27.51, Marc Mutz wrote:
Hi,
I was wondering whether we should stop using the pattern of declaring
_q_privateSlots() in favour of connecting to functors or functions
directly.
Makes sense, except
Hi,
On 11/10/2012, at 3:04 PM, ext Thomas McGuire wrote:
the QML engine freezes the global JS object. This is apparently(?) to
prevent accidental writes to the global object. For those who don't know, the
global object in JS provides objects and properties available in global
scope,
On Thu, Oct 11, 2012 at 04:23:43PM -0700, Thiago Macieira wrote:
On quinta-feira, 11 de outubro de 2012 18.44.39, Stephen Chu wrote:
I just installed mingw-build 4.7.2 on Windows 7 64-bit. I then
configured Qt 5 this way:
configure -developer-build -opensource -confirm-license -nomake
On Friday 12 October 2012 10:26:04 Olivier Goffart wrote:
On Thursday 11 October 2012 23:06:18 Thiago Macieira wrote:
On sexta-feira, 12 de outubro de 2012 07.27.51, Marc Mutz wrote:
Hi,
I was wondering whether we should stop using the pattern of declaring
_q_privateSlots() in
On Friday 12 October 2012 12:08:59 Marc Mutz wrote:
On Friday October 12 2012, Thiago Macieira wrote:
On sexta-feira, 12 de outubro de 2012 07.27.51, Marc Mutz wrote:
R2: less space used in meta-object
True, but minimal impact.
QLineEdit has up to seven _q_ slots, vs. up to eight
On Fri, 12 Oct 2012 10:10:59 +, Bache-Wiig Jens wrote:
True. There are certainly plenty of valid use cases out there and some
of those would require a minor change in Qt5 if we go ahead with this
change.
Basically it is about if you want to have a pen width in model or paint
device
Hi,
On Friday 12 October 2012 10:17:20 Jedrzej Nowacki wrote:
On Thursday 11. October 2012 16.04.04 Thomas McGuire wrote:
Could we maybe simple get rid of object freezing, and not freeze the
global object?
What would the consequences of that be, anything bad? I am the opinion
that if the
Hi,
On Friday 12 October 2012 12:16:26 aaron.kenn...@nokia.com wrote:
On 11/10/2012, at 3:04 PM, ext Thomas McGuire wrote:
the QML engine freezes the global JS object. This is apparently(?) to
prevent accidental writes to the global object. For those who don't know,
the global object in JS
Hi,
On Thursday 11 October 2012 17:36:55 Harri Porten wrote:
On Thu, 11 Oct 2012, Thomas McGuire wrote:
Could we maybe simple get rid of object freezing, and not freeze the
global object?
What would the consequences of that be, anything bad? I am the opinion
that if the user wants to
Basically it is about if you want to have a pen width in model or paint
device coordinates. Both use cases exist and IMHO none of them is more
important than the other.
Agree on the importance on both but the inconsistency applies in both use cases.
Most likely no more than
On Fri, 12 Oct 2012 12:21:30 +, Bache-Wiig Jens wrote:
I will leave that question for the graphics guys. I find it really
strange that the performance impact of this would be significant and
doubt that this is currently the case but I could easily be mistaking.
In Qwt I have an example
Hi,
On Friday 12 October 2012 13:30:57 Thomas McGuire wrote:
I've also been thinking about adding the frozen global object to the
snapshot, but I think that will not work. Qt changes the global object, for
example by adding the qsTr() function, so freezing would have to happen
after Qt is
On Fri, 12 Oct 2012 12:21:30 +, Bache-Wiig Jens wrote:
After all what is the point of doing a
major version unless we don't even allow ourselves to change broken
defaults.
There is nothing broken: it's a well defined API that behaves exactly
like it is documented. Your suggestion is
Thiago Macieira schreef op do 11-10-2012 om 16:11 [-0700]:
On quinta-feira, 11 de outubro de 2012 21.16.56, Oswald Buddenhagen wrote:
oh, i'm not worried about the work. saying no is easy. the patches would
of course be written by those who want the changes. ;)
I'm willing to put in the
On 10/12/2012 03:17 PM, Uwe Rathmann wrote:
On Fri, 12 Oct 2012 12:21:30 +, Bache-Wiig Jens wrote:
After all what is the point of doing a
major version unless we don't even allow ourselves to change broken
defaults.
There is nothing broken: it's a well defined API that behaves exactly
On sexta-feira, 12 de outubro de 2012 12.08.59, Marc Mutz wrote:
True, but minimal impact.
QLineEdit has up to seven _q_ slots, vs. up to eight normal ones (exact
number depends on #ifdefs). But yes, I need to measure whether the
reduction in the meta-object isn't offset by the extra code
On Friday October 12 2012, Olivier Goffart wrote:
On Friday 12 October 2012 10:26:04 Olivier Goffart wrote:
On Thursday 11 October 2012 23:06:18 Thiago Macieira wrote:
On sexta-feira, 12 de outubro de 2012 07.27.51, Marc Mutz wrote:
Hi,
I was wondering whether we should stop
On Friday October 12 2012, Thiago Macieira wrote:
Not harder to use than Q_PRIVATE_SLOT, IMO. More annoying, yes, because
of boilerplate code (of which Q_PRIVATE_SLOT also has some, mind).
Real-life example:
[snip]
I'd rather explore options like what Olivier is proposing. The functors,
I think Windows also uses 0-width to mean the same thing.
On the other hand, I worked on a drawing library that used sub-pixel lines.
Via good anti-aliasing, A 0.5 width line, even if vertical/horizontal, would be
drawn semi-transparent. A 0-width line would thus be invisible.
Hi,
On 10/12/2012 08:29 AM, Thiago Macieira wrote:
Since no one has spoken up, that means we have the official Qt 5.0 release
list.
It will include the following Git repositories:
qtbase
qtwebkit
qtquick1
qtdeclarative
qttools
qtwebkit
A couple of people have requested this:
http://lists.qt-project.org/pipermail/releasing/2012-September/000634.html
This is from the Director of Qt RD at Digia, so I think you can count
on it. The SDK is dead for non commercial customers. If you disagree,
you just might have found your new pet
On sexta-feira, 12 de outubro de 2012 18.51.28, Sergio Ahumada wrote:
Hi,
On 10/12/2012 08:29 AM, Thiago Macieira wrote:
Since no one has spoken up, that means we have the official Qt 5.0 release
list.
It will include the following Git repositories:
qtbase
qtwebkit
On 13/10/2012, at 12:47 AM, Shawn Rutledge shawn.t.rutle...@gmail.com wrote:
I got started working on QScreen, its properties, notifiers, and
implementation on all 3 platforms after I noticed that the
documentation was out of sync with the implementation in Qt5.
[on a side note]
While
On 12 October 2012 21:03, Lorn Potter lorn.pot...@gmail.com wrote:
On 13/10/2012, at 12:47 AM, Shawn Rutledge shawn.t.rutle...@gmail.com wrote:
I got started working on QScreen, its properties, notifiers, and
implementation on all 3 platforms after I noticed that the
documentation was out of
28 matches
Mail list logo
