We are happy to share the results of our work on cross-platform high-DPI
scaling in Qt, which is planned for Qt 5.6. It is now at a stage where it can
be tested by others. You can get the code from our branch in qtbase:
wip/highdpi. The branch is open for business, and contributions are welcome.
On 06/04/2015 04:52 PM, Konstantin Ritt wrote:
> #define Q_OBJECT \
>
> public: \
>
> Q_OBJECT_CHECK \
>
> QT_WARNING_PUSH \
>
> Q_OBJECT_NO_OVERRIDE_WARNING \
>
> static const QMetaObject staticMetaObject; \
>
> virtual const QMetaObject *metaObject() const;
On Thu, Jun 04, 2015 at 12:41:23PM +, Bornemann Joerg wrote:
> > 1) Add "override" (or rather Q_DECL_OVERRIDE) to the definition of
> > Q_OBJECT *and* all QObject-derived classes in Qt.
> [...]
> > 2) Remove "override" from all QObject-derived classes in Qt.
> [...]
> > 3) Explicitly disable th
#define Q_OBJECT \
public: \
Q_OBJECT_CHECK \
QT_WARNING_PUSH \
Q_OBJECT_NO_OVERRIDE_WARNING \
static const QMetaObject staticMetaObject; \
virtual const QMetaObject *metaObject() const; \
virtual void *qt_metacast(const char *); \
virtual int qt_metacall(QMetaOb
On 2015-06-04 08:12, Christian Kandeler wrote:
> as anyone who uses clang has probably already noticed, this compiler has
> recently added "-Winconsistent-missing-override" to the collection of
> flags enabled via "-Wall".
What happens if you (push state and) disable the warning at the start of
On Thu, Jun 4, 2015 at 2:41 PM, Bornemann Joerg
wrote:
>
>> 1) Add "override" (or rather Q_DECL_OVERRIDE) to the definition of
>> Q_OBJECT *and* all QObject-derived classes in Qt.
> [...]
>> 2) Remove "override" from all QObject-derived classes in Qt.
> [...]
>> 3) Explicitly disable the warning i
It's time for the header diffs, please help review the changes (Qt 5.4.2 to
5.5.0) to make sure nothing that was added to the public headers slipped
through when it shouldn't be there.
I'll send mails in reply to this one with the diffs attached (that will take a
while).
Cheers,
Frederik
Outp
> 1) Add "override" (or rather Q_DECL_OVERRIDE) to the definition of
> Q_OBJECT *and* all QObject-derived classes in Qt.
[...]
> 2) Remove "override" from all QObject-derived classes in Qt.
[...]
> 3) Explicitly disable the warning in the clang mkspecs.
[...]
> 4) Let users deal with the problem b
Hi,
as anyone who uses clang has probably already noticed, this compiler has
recently added "-Winconsistent-missing-override" to the collection of
flags enabled via "-Wall". As a result, you now get literally thousands
of warnings when building any non-trivial Qt project. This is because
the e
