gsettings-qt bi-directional binding can cause X lockup

[[e-mail]]

Bi-directional bindin can cause a lockup of X.
Would be good to check inside gsettings-qml something like:
void setValue
 ( m_value != value )
    {
        m_value = value;
        emit valueChanged();
    }
}

Example code:
http://pastie.org/9293986

[Lars Karlitski (larsu)]

I agree, this makes sense for the qml bindings. We can't do it for the c++ class in the same project, because that doesn't cache the values like QQmlPropertyMap does.

Thanks for reporting this!

[[e-mail] (damianatorrpm)]

While we're at data binding, somewhat related https://bugs.launchpad.net/gsettings-qt/+bug/1333460

[[e-mail] (damianatorrpm)]

https://bugs.launchpad.net/gsettings-qt/+bug/1333460 is my bad, please close it.

[Launchpad Janitor (janitor)]

This bug was fixed in the package gsettings-qt - 0.1+14.10.20140624-0ubuntu1

---------------
gsettings-qt (0.1+14.10.20140624-0ubuntu1) utopic; urgency=low

  [ Lars Uebernickel ]
  * Stop using deprecated g_settings_get_range()
  * qml: only emit changed when the value has actually changed This
    cannot be done for the c++ class, because that would involve a
    round-trip to the dconf database. The QML component already caches
    all values because of the way QQmlPropertyMap works. (LP: #1330365)
 -- Ubuntu daily release <email address hidden> Tue, 24 Jun 2014 10:01:54 +0000