3 ms·
In my view it would have been OK if force touch had been equivalent to a long hold. The problem is that force touch and long hold do different things.
by nicky0 11y ago
In my view it would have been OK if force touch had been equivalent to a long hold. The problem is that force touch and long hold do different things.
- derefr 11y agoIn my view, a long hold was always basically a "secondary click"—but Apple didn't use it for much, since it was so tedious. So, rather than getting a menu, it mostly served to activate a single important secondary function on the item. (And devs came up with different solutions for menus, like side-swiping in list-views; and modal multi-select, with additional actions to apply to selected results.) Force touch, on the other hand, isn't tedious, so it does what Apple wanted to do: it gives you a menu. I would expect that whatever a long hold does to an item should also be a thing on that menu. You could think of a long hold, then, as the "default secondary action"—like how shell object handlers in Windows use their "default primary action" from their context menu when double-clicked.