[ad_1]
The smooth running of the Chromebook trackpad is one thing I've always liked about Chromebooks. As gestures were added and better materials were used to build them, the Chrome OS trackpad has steadily improved over time. Compared to the years of terrible trackpads for Windows laptops My time with Chromebook trackpads was one of the highlights of this experience.
During this period, I got used to a handful of gestures to navigate my devices. One, two, three and even four finger gestures are great ways to increase productivity and handle tasks faster and easier. Switching to Overview mode with a 3-finger swipe or scanning my open tabs with a 3-finger left / right sweep has become a habit that dominates my daily routines. But now, I see evidence that these routines may be a little shaken. Discover this commit and its rather clear language:
Virtual desktops and overview change the number of fingers
– Cleaning Tabs: Use 4-finger gestures.
– Office switch: Use 3-finger gestures.
– Selecting the overview: use 4-finger gestures.
This change is being tested and will involve all current gestures using 3 or 4 fingers. In general, it seems like they'll just swap the current 3-finger gestures so that they now require 4 fingers and make sure that the 4-finger Virtual Desk switch gestures only require three fingers.
I am convinced that the simpler the task, the easier the gesture must be. In this context, I think that the current configuration is quite logical. Switching to Overview mode or switching from one tab to the other is a much smaller movement than switching from one virtual office to another. So I think it's more intuitive to make the gesture more complex more complex.
Buy Chromebooks on Amazon
For users like me used to these gestures, It will be a difficult transition and I do not quite understand why this is even necessary. Maybe the scroll mode tabs and overviews are triggering a little too easily and too frequently and they want to eliminate this error from the equation for users. I have trouble finding any other reasons for this change, but it seems that it is merged into Chrome OS 78 and that it is evolving with or without my consent. =)
[ad_2]
Source link