mirror of
https://github.com/Hopiu/micro.git
synced 2026-04-15 20:01:04 +00:00
2d95064ff6
Since now bufpane handles mouse move and release events generically and separately from mouse press events, that creates a mess when we dispatch a mouse press event to an inactive pane without making it active. For example: 1. Click the right button on an inactive pane. It remains inactive. 2. Then click the left button on it. It becomes active, and an unexpected text selection appears. The reason is that the release event for the first click was dispatched to a wrong pane - the (then) active one, so the (then) inactive pane didn't get the release event and treats the second click not as a mouse press but as a mouse move. The simplest way to fix it is to avoid this scenario entirely, i.e. always activate the pane when clicking any mouse button on it, not just the left button. For mouse wheel motion events we keep the existing behavior: the pane gets the event but doesn't become active. Mouse wheel motion events are not affected by the described issue, as they have no paired "release" events. |
||
|---|---|---|
| .. | ||
| actions.go | ||
| actions_other.go | ||
| actions_posix.go | ||
| bindings.go | ||
| bufpane.go | ||
| command.go | ||
| defaults.go | ||
| defaults_darwin.go | ||
| defaults_other.go | ||
| events.go | ||
| globals.go | ||
| infocomplete.go | ||
| infopane.go | ||
| keytree.go | ||
| pane.go | ||
| rawpane.go | ||
| tab.go | ||
| terminal_supported.go | ||
| terminal_unsupported.go | ||
| termpane.go | ||