| commit | a06fbabc24c0eedc5ccae5e527e4fed6823b65c2 | |
| author | Ryan Lortie <desrt@desrt.ca> | |
| Wed, 27 Nov 2013 18:03:51 +0000 (27 13:03 -0500) | ||
| committer | Ryan Lortie <desrt@desrt.ca> | |
| Wed, 27 Nov 2013 18:03:51 +0000 (27 13:03 -0500) | ||
| tree | 0f6996ccf417fdd72ed35034cdd1c87b0910eebf | treesnapshot (tar.gz zip) |
| parent | 615cbd7990f29d70dca33282695b3a0bbeb89cde | commitdiff |
engine: filter change signals properly
Testing revealed that we were transmitting any change signal that came
in from the bus up to user code, even if the engine in question was not
interested in receiving the signal.
This is a problem in the case that two DConfClient objects exist for
different profiles. In that case, we'd get crosstalk between the
subscriptions that each client had made and change notifications would
appear in both clients even if the change only affected one.
Testing revealed that we were transmitting any change signal that came
in from the bus up to user code, even if the engine in question was not
interested in receiving the signal.
This is a problem in the case that two DConfClient objects exist for
different profiles. In that case, we'd get crosstalk between the
subscriptions that each client had made and change notifications would
appear in both clients even if the change only affected one.
| engine/dconf-engine.c | diffblobblamehistory |