After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 747434 - InputSettings: apply mouse natural scroll settings at startup
InputSettings: apply mouse natural scroll settings at startup
Status: RESOLVED FIXED
Product: mutter
Classification: Core
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: mutter-maint
mutter-maint
: 747838 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2015-04-07 04:15 UTC by Giovanni Campagna
Modified: 2015-04-14 14:31 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
InputSettings: apply mouse natural scroll settings at startup (1.06 KB, patch)
2015-04-07 04:15 UTC, Giovanni Campagna
none Details | Review
input-settings: Ensure that we always apply the same set of settings (9.49 KB, patch)
2015-04-14 13:39 UTC, Rui Matos
committed Details | Review

Description Giovanni Campagna 2015-04-07 04:15:28 UTC
Seems it was forgotten
Comment 1 Giovanni Campagna 2015-04-07 04:15:30 UTC
Created attachment 301044 [details] [review]
InputSettings: apply mouse natural scroll settings at startup
Comment 2 Rui Matos 2015-04-07 08:52:21 UTC
Looks like it's also missing from _device_added() . Carlos, is there a reason for this?
Comment 3 Carlos Garnacho 2015-04-07 09:11:43 UTC
Oops, not really, forgotten as Giovanni pointed out. I remember the natural scroll setting for non-touchpads was a "why not" afterthought, I didn't test as thoroughly as with touchpads apparently...
Comment 4 Ondrej Holy 2015-04-14 11:05:03 UTC
*** Bug 747838 has been marked as a duplicate of this bug. ***
Comment 5 Rui Matos 2015-04-14 13:39:38 UTC
Created attachment 301544 [details] [review]
input-settings: Ensure that we always apply the same set of settings

This makes the hotplug and coldplug paths the same so that we don't
miss out on any setting.
--

I think we should go with something like this to avoid further
mistakes.
Comment 6 Rui Matos 2015-04-14 13:41:45 UTC
*** Bug 747838 has been marked as a duplicate of this bug. ***
Comment 7 Carlos Garnacho 2015-04-14 13:57:33 UTC
Comment on attachment 301544 [details] [review]
input-settings: Ensure that we always apply the same set of settings

Looks right to me. I'd perhaps change the

+      if (type == CLUTTER_POINTER_DEVICE)
+        enabled = g_settings_get_boolean (priv->mouse_settings, key);
+      else if (type == CLUTTER_TOUCHPAD_DEVICE)
+        enabled = g_settings_get_boolean (priv->touchpad_settings, key);

parts to use a get_settings_for_device() kind of function.
Comment 8 Rui Matos 2015-04-14 14:31:05 UTC
(In reply to Carlos Garnacho from comment #7)
> parts to use a get_settings_for_device() kind of function.

Ok, pushed with something along those lines. Thanks

Attachment 301544 [details] pushed as 8769b3d - input-settings: Ensure that we always apply the same set of settings