On Wed, 21 Sep 2011 23:43:34 +0200, Thiago Macieira thi...@kde.org wrote:
What is worse for you, that someone unintentionally emits a signal, or
that
you fail to connect because someone made a typo, or accidentally left the
variable names in the SIGNAL or SLOT definition. Not to mention in
On Wednesday 21 September 2011 19:09:11 ext Thiago Macieira wrote:
Is it really nessecairy that _everyone_ has public access to the signal?
What if only QObject had access to it? Would that work? If so, it could
work to just make QObject a friend class of every class that has the
Q_OBJECT
On 9/21/11 5:09 PM, ext Wolf-Michael Bolle
wolf-michael.bo...@nokia.com wrote:
On Wednesday 21 September 2011 15:19:59 ext Иван Комиссаров wrote:
I explored native mime database in Windows. It is stored in registry and
contains data for most common extensions. It is a map from *.extension
to
Hi Thiago,
On Tuesday August 23 2011, Thiago Macieira wrote:
Moreover, imagine an embedded device that wants to save space in the
minimal base system: they could choose to compile Qt and all of their
applications without STL, thus saving a few hundred kilobytes of libstdc++.
But user
On Thu, Sep 22, 2011 at 8:31 AM, Wolf-Michael Bolle
wolf-michael.bo...@nokia.com wrote:
Why doesn't a class simply provide public connector method templates for the
not so public signals?
// Very simplified example
class Xyz
{
private:
void eventHasHappened(); // A signal
public:
On Thursday, 22 de September de 2011 09:08:02 Marc Mutz wrote:
Hi Thiago,
On Tuesday August 23 2011, Thiago Macieira wrote:
Moreover, imagine an embedded device that wants to save space in the
minimal base system: they could choose to compile Qt and all of their
applications without STL,
On Thursday 22 September 2011 09:08:02 ext Marc Mutz wrote:
Hi Thiago,
On Tuesday August 23 2011, Thiago Macieira wrote:
Moreover, imagine an embedded device that wants to save space in the
minimal base system: they could choose to compile Qt and all of their
applications without STL,
OK, but it is important that there are some fulltime developers.
Why? Why are 2 full-time developers better than 20 part-time ones?
I'd love to have full-time developers working on this, but I'll take what
I
can get. Besides, if you look at any feature over a reasonably long period
of
Hello,
it might be a good idea to make QImage colorspace aware and add some other
color formats (like 30 bit or floating point formats).
This might be useful for a fully color managed desktop environment, too. I am
not sure how this will work in wayland. Either the compositor applies the
On Thursday 22 September 2011 08:18:49 Frans Klaver wrote:
[...]
I'm still not convinced that the trade-off is worth your while, but you
obviously think it is. There's downsides and upsides to both approaches.
Compile-time check is one thing, but there is also other advantage of the new
code.
On Thu, Sep 22, 2011 at 1:47 PM, Olivier Goffart oliv...@woboq.com wrote:
- You get automatic conversions of the arguments (eg. QString-QVariant or
int-double, ...)
I didn't consider this one.
- You get all the power of connecting using tr1::bind, or to a C++11 lambda
expression.
There
On Thu, Sep 22, 2011 at 2:06 PM, Olivier Goffart oliv...@woboq.com wrote:
class Foo {
public:
class Signal { //This would be in the Q_OBJECT macro.
~Signal() {}; // private destructor
friend class Foo; //- problem: Q_OBJECT macto does not know Foo
};
Signal
Am 21.09.2011 um 19:50 schrieb Uwe Rathmann uwe.rathm...@tigertal.de:
On Wed, 21 Sep 2011 16:11:03 +0200, Thiago Macieira wrote:
First, that's extremely vague. I can simply answer that with QML it's
easier to do things against the toolkit
I had to implement an application where the
- Original Message -
From: Thiago Macieira thi...@kde.org
To: qt5-feedback@qt.nokia.com
Cc:
Sent: Thursday, September 22, 2011 11:33 AM
Subject: Re: [Qt5-feedback] QObject: new signals-slots syntax
On Thursday, 22 de September de 2011 14:06:05 Olivier Goffart wrote:
I almost
14 matches
Mail list logo
