gsettings-qt bi-directional binding can cause X lockup
Bug #1330365 reported by
damianatorrpm@gmail.com
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gsettings-qt |
In Progress
|
Undecided
|
Lars Karlitski | ||
gsettings-qt (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
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://
Related branches
lp://staging/~larsu/gsettings-qt/lp1330365
- Iain Lane (community): Approve
- PS Jenkins bot: Approve (continuous-integration)
-
Diff: 16 lines (+4/-2)1 file modifiedGSettings/gsettings-qml.cpp (+4/-2)
To post a comment you must log in.
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!