> Lars wrote:
> > This is mostly done. What remains is the renaming of the classes from
> > QDeclarative to QQuick/QQml. This is ok for me to go into api_changes
> > (you might need to create that branch in qtdeclarative) with the
> > compat hacks we have (in moc and qtdeclarative).
> >
> > Please
On Sun, 4 Mar 2012 03:15:40 ext Alberto Mardegan wrote:
> Hi all,
> sorry for the intricated subject, I couldn't find a concise and
> understandable way to express what I mean. :-)
>
> Often it happens to me that I want to run some code when two or more
> properties change on a QML object. A rea
On domingo, 4 de março de 2012 23.49.03, John Layt wrote:
> In the QLocale header we have the following code:
>
> //private:
> // this should be private, but can't be
> struct Data {
> quint16 index;
> quint16 numberOptions;
> };
> private:
>
Hi,
In the QLocale header we have the following code:
//private:
// this should be private, but can't be
struct Data {
quint16 index;
quint16 numberOptions;
};
private:
friend struct QLocalePrivate;
// ### We now use this field t