Dear all:
I'm learning to use the Phonon in QT, followed up some examples in the help
document to setup one VideoPlayer, but when running this programe, it always
crashed, the example is so simple I don't known where is wrong.
#include
#include
#include
int main(int argc, char *argv[]) {
Sounds good to me. Sergio or Rohan, can you help, please?
Thanks,
Lars
On 2/17/12 7:04 PM, "ext Anselmo L. S. Melo"
wrote:
>Hi,
>
>I would like to continue the work started with the change 15857 [1], when
>we discussed about moving QUndo* out of QtWidgets.
>In this change, first we moved these
On Tue, Feb 14, 2012 at 7:55 PM, Mark wrote:
> On Tue, Feb 14, 2012 at 7:44 PM, Robin Burchell wrote:
>
>> Hi Mark,
>>
>> 2012/2/14 Mark :
>> > Could someone please patch this in Qt (4.8.x as well?).. I don't have an
>> > account for review/commit stuff. Feel free to commit :)
>>
>> I'd strongly
Hi,
I would like to continue the work started with the change 15857 [1], when we
discussed about moving QUndo* out of QtWidgets.
In this change, first we moved these classes to QtGui, then to a new lib inside
qtbase. However, it was not considered ideal and the
decision was to create a separated
I answer to myself.
If add in serialport_global.h also these lines:
..
#if defined QT_BEGIN_MOC_NAMESPACE
# undef QT_BEGIN_MOC_NAMESPACE
#endif
#if defined QT_END_MOC_NAMESPACE
# undef QT_END_MOC_NAMESPACE
#endif
#define QT_BEGIN_MOC_NAMESPACE QT_BEGIN_NAMESPACE_SERIALPORT
#define QT_END_MOC_NA
Currently we continue to have the Qt 4 printing subsystem in Qt5 (as
libQtPrintSupport), but the longer term plan is to replace this with a new
module, as some of the basic architecture of the old printing module is
not fixable.
For 5.0 however we continue with what we have.
Cheers,
Lars
On 2/17
Hi list,
there is a rather heated discussion in a 3 years old kde bug [1] regarding
printing, more specifically the print dialog and how it should keep/save
settings between different call of it.
Could you (as somebody involved in qt5 planning or development) clarify what
the plan are for pr
Hi all,
We had a discussion (a while back) with Lars, Martin, Aaron, Roberto, Alex
and others about the module versioning in Qt 5: why we have versioned
import statements in QML, how backwards compatibility in C++ and QML can
be maintained, and if there is something we could do to make the module
On 17/02/2012 07:27, ext Thiago Macieira wrote:
> On sexta-feira, 17 de fevereiro de 2012 13.20.09,
> marius.storm-ol...@nokia.com wrote:
>> On 17/02/2012 05:39, ext Thiago Macieira wrote:
>>> On sexta-feira, 17 de fevereiro de 2012 01.47.13,
>>>
>>> andrew.den-ex...@nokia.com wrote:
I'm not s
On 2/17/12 2:24 PM, "ext marius.storm-ol...@nokia.com"
wrote:
>On 17/02/2012 05:41, ext Thiago Macieira wrote:
>> On sexta-feira, 17 de fevereiro de 2012 09.19.20,
>> eike.zil...@nokia.com wrote:
>>> Why would that mean to reject
>>> http://codereview.qt-project.org/16019 ?
>>>
>>> It just adds f
On sexta-feira, 17 de fevereiro de 2012 13.20.09, marius.storm-ol...@nokia.com
wrote:
> On 17/02/2012 05:39, ext Thiago Macieira wrote:
> > On sexta-feira, 17 de fevereiro de 2012 01.47.13,
> >
> > andrew.den-ex...@nokia.com wrote:
> >> I'm not saying there won't be any maintenance burden, but it's
On 17/02/2012 05:41, ext Thiago Macieira wrote:
> On sexta-feira, 17 de fevereiro de 2012 09.19.20,
> eike.zil...@nokia.com wrote:
>> Why would that mean to reject
>> http://codereview.qt-project.org/16019 ?
>>
>> It just adds files that could be used for building Qt Creator with
>> qbs, but it doe
On 17/02/2012 05:39, ext Thiago Macieira wrote:
> On sexta-feira, 17 de fevereiro de 2012 01.47.13,
> andrew.den-ex...@nokia.com wrote:
>> I'm not saying there won't be any maintenance burden, but it's not
>> massively greater than a lot of other modules either.
>
> I'll take your word for it.
>
>
Hi, all.
I am developing a new addon for Qt5 in Gerrit /playground/QtSerialPort and I
have a
problem with the macros QT_BEGIN_NAMESPACE_SERIALPORT,
QT_END_NAMESPACE_SERIALPORT and etc.
With this code in the global file serialport-global.h
..
#ifndef SERIALPORT_GLOBAL_H
#define SERIALPORT_GLOBA
On sexta-feira, 17 de fevereiro de 2012 14.09.05, Kumar-Kuntala Kranthi wrote:
> Hi,
>
> In continuation to the discussion we had some time time ago merge former
> mobility systeminfo Api's QSystemAlignedtimer to QTimer.
>
> http://lists.qt-project.org/pipermail/development/2011-November/000526.htm
Hi,
In continuation to the discussion we had some time time ago merge former
mobility systeminfo Api's QSystemAlignedtimer to QTimer.
http://lists.qt-project.org/pipermail/development/2011-November/000526.html
I would like to keep QSystemAlignedtimer as a separate class and not to
merge in QTi
On 2/17/12 12:39 PM, "ext Atlant Schmidt"
wrote:
>João:
>
>> I think the even better approach, once the necessary changes are done
>> inside Qt and things settle down, is to drop qreal completely. Don't
>> pick float or real, don't define it. Or typedef it to some dummy type:
>>
>>class qreal
On Friday, February 17, 2012 07:06:16 Konrad Rosenbaum wrote:
> On Wednesday 15 February 2012, Stephen Kelly wrote:
> > On Wednesday, February 15, 2012 21:55:54 Konrad Rosenbaum wrote:
> > > The
> > >
> > > calculation results are almost identical. Almost.
> >
> > Is that enough?
> >
> > John L
On sexta-feira, 17 de fevereiro de 2012 09.19.20, eike.zil...@nokia.com wrote:
> Why would that mean to reject http://codereview.qt-project.org/16019
> ?
>
> It just adds files that could be used for building Qt Creator with qbs, but
> it doesn't disrupt anybody's workflow as long as they use qmake
João:
> I think the even better approach, once the necessary changes are done
> inside Qt and things settle down, is to drop qreal completely. Don't
> pick float or real, don't define it. Or typedef it to some dummy type:
>
>class qreal_IsNoMore {};
>typedef qreal_IsNoMore qreal;
>
> Force
On sexta-feira, 17 de fevereiro de 2012 01.47.13, andrew.den-ex...@nokia.com
wrote:
> I'm not saying there won't be any maintenance burden, but it's not massively
> greater than a lot of other modules either.
I'll take your word for it.
What I'm still looking for is that someone comes out and say
Ben wrote:
> The concerns are not the signals/slots. Yes, that is one aspect.
> The concern is other code that uses qreal - e.g. people embedding it
> in binary protocols, or using it in printf()'s, etc.
> The vast majority of Qt is probably in the desktop arena, and there
> qreal is a double; and
> -Original Message-
> From: Beck Wolfgang (Nokia-MP/Brisbane)
> Sent: Friday, February 17, 2012 3:58 AM
> To: Koehne Kai (Nokia-MP/Berlin); development@qt-project.org
> Subject: QT_MESSAGE_PATTERN
>
> Hi Kai,
Hi Wolfgang,
> I'm trying to use the QMessagePattern and I'm missing some doc
On Thu, Feb 16, 2012 at 11:26:24PM +0400, ext Denis Shienkov wrote:
> Oops... Oswald, tell me please, what happened to the repo project
> QtSerialPort of the Gerrit playground? What to do now? :)
>
err, i messed up the permissions. sorry. fixed.
> Best regards,
> Denis
>
> 16.02.2012, 22:05, "O
On 16 Feb 2012, at 13:35, ext Thiago Macieira wrote:
> On quinta-feira, 16 de fevereiro de 2012 12.47.02, Mathias Hasselmann wrote:
>>> But if the qbs devs want to start adding files to the Qt installation like
>>> the current pkg-config, cmake and libtool files, they can. I would
>>> personally
On Friday 17 February 2012 09:19:04 Lincoln Ramsay wrote:
> > The goal: that global_enabled() affects *all* qDebug statements, not only
> > those with a category
>
> Unlike qLog (which defaults to off), qDebug must be on by default or we
> break all existing code. This means a "runtime" switch for
26 matches
Mail list logo