Don't override user control of swipe action
By danh... on June 02, 2011 00:59 (imported from Google Code)
What steps will reproduce the problem?
- Map a swipe action in an app such as MultiClutch
- Attempt the swipe action, with or w/o restarting iTerm2
- Observe that nothing happens aside from the iterm2 change-tab behavior
What is the expected output? What do you see instead?
I have custom swipe mappings which I have used w/o issue under the old iTerm. By capturing all swipe events but narrowly construing their behavior (based on a single previous request http://code.google.com/p/iterm2/issues/detail?id=567) you remove that flexibility. Providing an override/disable option to this (which does not "eat" all swipe options) or providing full swipe mapping support would alleviate this issue. Even just a "hidden" disable option would be better than nothing.
One man's feature is another man's bug - it's best not to blanket capture UI input to provide a subset of functionality :) Please consider the likely advanced nature of your intended userbase. We're not looking a better terminal -- and specifically, a better iTerm -- in order to have its features curtailed :)
For instance, I map three-finger swipe up and down to up and down arrows, right swipe to ^V, and left swipe (through some monkeying) to clear-line. I don't expect that others do, but ATM all swipes are being consumed rather than passed through if unrecognized.
What version of the product are you using? On what operating system?
iTerm2 Build 0.20.20110529 on 10.5.8
Please provide any additional information below.