Actually as it appears from the discussion of bug 1467851, I'm afraid that the fix for this bug will completely remove the warning, because the QML context is always null (I have an application actively using the "theme" context property, and yet the context is empty for it, too).
Anyway, looking forward for the fix to land in vivid :-)
Actually as it appears from the discussion of bug 1467851, I'm afraid that the fix for this bug will completely remove the warning, because the QML context is always null (I have an application actively using the "theme" context property, and yet the context is empty for it, too).
Anyway, looking forward for the fix to land in vivid :-)