From kde-games-devel  Thu Aug 08 22:43:12 2013
From: =?UTF-8?B?0JTQtdC90LjRgSDQmtGD0L/Qu9GP0LrQvtCy?= <dener.kup () gmail ! com>
Date: Thu, 08 Aug 2013 22:43:12 +0000
To: kde-games-devel
Subject: Re: [Kde-games-devel] KDE theme colors API for QML
Message-Id: <CAKHG4a3WSQmVVZrL7qWjQw-C31PRM8aeGLkaLGw-PkBTacq+3A () mail ! gmail ! com>
X-MARC-Message: https://marc.info/?l=kde-games-devel&m=137600183208861

> In case you are referring to C++ code that is currently using KColorScheme
> enums, then no, that code can stay unchanged.

I don't understand how it can be made? I have seen many uses like
KColorScheme::NormalBackground, but it will need to be rewriten to
BackgroundRole::NormalBackground if BackgroundRole is wrapper class
for enum?

> Any QML adapter would simply translate the values.
> If the enums of the adapter are equal to the one of KColorScheme (which is
> likely because this is the desired use), then "translating" is a simple cast.

Still we need to stay in sync between this adapter and KColorScheme
enums that is not good in part of maintaining code.

I still want to know about is Q_GADGET solution or not?
_______________________________________________
kde-games-devel mailing list
kde-games-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-games-devel