I think the issue had to do with: https://bugreports.qt-project.org/browse/QTBUG-36849
And after building from git the errors have gone away. Still think it would be nice if binding loops had a bit of a stack trace if its feasible... which has already been suggested :) https://bugreports.qt-project.org/browse/QTBUG-36525 Sorry for the spam Preet On Wed, Mar 12, 2014 at 11:49 PM, Preet <[email protected]> wrote: > Hi, > > After upgrading QtQuick recently (from 5.2-beta iirc to whatever the > stable branch of 5.2 was pointing to a few of weeks ago) I seem to be > getting a ton of additional Binding loop errors in QML that I didn't > get before (qmake says I'm on 5.2.2). > > As a quick example, I get a complaint that there's a binding loop > error for the following: > > property url font_fira: path_fonts + "FiraSans-Regular.ttf"; > property variant fl_font_default: FontLoader { id: fontDefault; > source: font_fira; } > > QML FontLoader: Binding loop detected for property "source" > > The code didn't generate any errors before. So... > * What changed to cause all these additional warnings? > * Is there a way to suppress them? > * Any idea what the specific example I posted is complaining about? > > Also are there any debugging methods I can use to trace out a binding > loop? In general, pointing to a line in a QML file doesn't really > provide enough information to figure out what's going on unless its a > trivial case. An extended call stack would help a lot. > > > Preet _______________________________________________ Interest mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/interest
