Hi,
Do I have your attention? Good :)
Since Qt 5.2 we support categorized logging in Qt, and the next logical step is
to also take it into good use inside the Qt libs. I'd therefore like to propose
changing qDebug, qWarning uses in the Qt code base into qCDebug, qCWarning , ...
Just for the re
On 8 January 2014 09:35, Koehne Kai wrote:
> - Current #ifdef's, environment variables etc should be replaced with an
> unconditional qCDebug/qCWarning/qCCritical
That's not doable in 100% of the cases, f.i. if one has to compile
extra code to get the debug information that needs to be printed.
> -Original Message-
> From: Giuseppe D'Angelo [mailto:dange...@gmail.com]
> Sent: Wednesday, January 08, 2014 9:54 AM
> To: Koehne Kai
> Cc: development@qt-project.org
> Subject: Re: [Development] Let's get rid of qDebug/qWarning/qCritical!
>
> On 8 January 2014 09:35, Koehne Kai wrote:
> -Original Message-
> From: development-bounces+kai.koehne=digia@qt-project.org
> [mailto:development-bounces+kai.koehne=digia@qt-project.org] On
> Behalf Of Koehne Kai
> Sent: Wednesday, January 08, 2014 10:13 AM
> To: Giuseppe D'Angelo
> Cc: development@qt-project.org
> Subject:
I have a controversial proposition: make qDebug/qWarning/qCritical support
logging category and deprecate qCDebug/qCWarning/qCCritical [1].
[1] https://codereview.qt-project.org/#change,74889
Regards,
Konstantin
2014/1/8 Koehne Kai
>
> > -Original Message-
> > From: development-bounc
> -Original Message-
> From: Konstantin Ritt [mailto:ritt...@gmail.com]
> Sent: Wednesday, January 08, 2014 10:39 AM
> To: Koehne Kai
> Cc: Giuseppe D'Angelo; development@qt-project.org
> Subject: Re: [Development] Let's get rid of qDebug/qWarning/qCritical!
>
> I have a controversial pro
> -Original Message-
> Subject: Re: [Development] Let's get rid of qDebug/qWarning/qCritical!
>
>
> [...]
> What you and André also seem to suggest is to keep the printf style . That's
> actually trivial to add to qCDebug and friends if we require support for
> variadic macros ... qcompil
Hi,
during the development of the new version of Qt3D's QML API we have come
across an interesting (well if you like that kind of thing) problem.
The issue is that at present the QML value type helpers for types such as
QVector3D are provided by QtQuick meaning that we have to do
import QtQuic
Sean Harmer sayeth:
> Hi,
>
> during the development of the new version of Qt3D's QML API we have come
> across an interesting (well if you like that kind of thing) problem.
>
> The issue is that at present the QML value type helpers for types such as
> QVector3D are provided by QtQuick meaning th
Hi,
I'd find it "natural" if there was something like a QtCore plugin.
Then, QtQuick and Qt3D (and other stuff) could depend on it; i.e.
something analogous to the existing Qt modules dependency, but in the
QML world.
I already encountered situations in which I wanted to use QtQuick
stuff
> -Original Message-
> From: development-bounces+kai.koehne=digia@qt-project.org
> [mailto:development-bounces+kai.koehne=digia@qt-project.org] On
> Behalf Of Sebastian Lehmann
> Sent: Wednesday, January 08, 2014 2:31 PM
> To: development@qt-project.org
> Subject: Re: [Development]
Hi,
As you might (or might not) know, nvidia introduced g-sync which is
going to be supported by some monitor vendors shipping monitors this
year.
AMD made a twist on that - smart as they are - by introducing their
own "FreeSync" which they claim is just using the vesa specification.
So no specia
On Wednesday 08 January 2014 16:07:10 Mark Gaiser wrote:
> Hi,
>
> As you might (or might not) know, nvidia introduced g-sync which is
> going to be supported by some monitor vendors shipping monitors this
> year.
>
> AMD made a twist on that - smart as they are - by introducing their
> own "Free
Hi guys,
We can write JS functions in QML, but they can't be passed around via
properties. The type "variant" can't be assigned a JS function.
Can either the possibility of such an assignment (to "variant"
properties) or a "function" property type be added to the QML core?
I'm not asking fo
This is already possible :) just use var properties, they map to QJSValue in
C++.
Simon
Fra: Sebastian Lehmann
Sendt: 19:31 onsdag 8. januar 2014
Til: development@qt-project.org
Emne: [Development] Builtin QML property type for functions possible?
Hi guys,
We can write JS functions in QML, bu
Hi,
The Qt documentation [1] point us that iOS minimum deployment target is
iOS 5.0
I tried to build a minimum application against iOS 5.0 SDK using Qt
5.2.0 libraries.
I got a linker error saying CTFontCopyDefaultCascadeListForLanguages is
undefined.
Indeed if I looked on Apple documentation [
To comment on the feasibility of raising the minimum deployment target...
4% of iOS devices are using iOS 5 or earlier (which means even less than 4% are
even using 5.x at all). IIRC, Xcode also no longer supports iOS 5.x simulators.
https://developer.apple.com/support/appstore/ (left side, scro
Yes, of course you are right, that's why Qt documentation should be changed.
Marius
On 1/8/14 9:43 PM, Jake Petroules wrote:
To comment on the feasibility of raising the minimum deployment target...
4% of iOS devices are using iOS 5 or earlier (which means even less
than 4% are even using 5.x
> -Original Message-
> From: Kurt Pattyn [mailto:kurt.pat...@icloud.com]
> On 08 Jan 2014, at 10:12, Koehne Kai wrote:
>
> >
> > You can then use it like that:
> >
> > If (qtCoreIo().isDebugEnabled()) {
> >QString x = expensive();
> >qCDebug(qtCoreIo) << "Expensive: " << x; }
>
Hi,
just FYI, there also is :
QVariant QPlatformNativeInterface::windowProperty(QPlatformWindow
*window, const QString &name) const;
void QPlatformNativeInterface::setWindowProperty(QPlatformWindow
*window, const QString &name, const QVariant &value);
which AFAIK currently is only used on Win
20 matches
Mail list logo
