On Monday 24 November 2014 23:00:45 Mirko Boehm wrote:
Hi Milian!
Man, I totally thought this is absolutely intuitive :-) I will write
something up as a blog post over the weekend. In the meantime, I am trying
to answer your question below.
On 24 Nov 2014, at 01:57, Milian Wolff
On Tuesday 25 November 2014 12:07:27 Milian Wolff wrote:
On Monday 24 November 2014 19:28:57 Thiago Macieira wrote:
On Monday 24 November 2014 23:00:45 Mirko Boehm wrote:
Can I inherit from QObjectDecorator and pass this as the
JobInterface
*decoratee?
The decorator wraps and
On 25 Nov 2014, at 04:28, Thiago Macieira thi...@kde.org wrote:
The decorator wraps and object and acts as a QObject. It does not really
care if the wrapped job is a QObject already. It will add defined signals
to the job.
Please don't create new classes named Q + Capital letter unless
Hi Milian!
Man, I totally thought this is absolutely intuitive :-) I will write something
up as a blog post over the weekend. In the meantime, I am trying to answer your
question below.
On 24 Nov 2014, at 01:57, Milian Wolff m...@milianw.de wrote:
Could you please document, e.g. by adding
On Monday 24 November 2014 23:00:45 Mirko Boehm wrote:
Can I inherit from QObjectDecorator and pass this as the JobInterface
*decoratee?
The decorator wraps and object and acts as a QObject. It does not really
care if the wrapped job is a QObject already. It will add defined signals
to
Hey All, esp. Mirko.
Could you please document, e.g. by adding another example, on how one is
supposed to use Job classes that are QObjects, i.e. have signals/slots? There
is this strange QObjectDecorator thingy which I don't quite get, it looks like
its supposed to add some signals to another
