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 758503 - API for querying mouse protocol
API for querying mouse protocol
Status: RESOLVED OBSOLETE
Product: vte
Classification: Core
Component: general
git master
Other Linux
: Normal enhancement
: ---
Assigned To: VTE Maintainers
VTE Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-11-22 19:48 UTC by Egmont Koblinger
Modified: 2021-06-10 15:07 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Egmont Koblinger 2015-11-22 19:48:03 UTC 
Once upon a time we fixed bug 13299 (for g-t to cleverly handle right click).

Now there's an analogous story https://bugs.launchpad.net/terminator/+bug/1505292. Terminator zooms on Ctrl+scroll, but a user wishes to see escape sequences. I think the ideal would be to see if the app handles mouse events, send those in that case, otherwise zoom.

vte_terminal_scoll(), however, always returns TRUE, since the widget always handles scroll events, one way or another.

How could we solve this problem? Maybe an explicit API to get whether mouse tracking is enabled?
Comment 1 Christian Persch 2015-11-22 20:13:57 UTC 
I guess this is about this block in ::widget_scroll() ?

	} else {
		/* Perform a history scroll. */
		double dcnt = m_screen->scroll_delta + v * m_mouse_smooth_scroll_delta;
		queue_adjustment_value_changed_clamped(dcnt);
		m_mouse_smooth_scroll_delta = 0;
	}

which you want to only run when no modifiers are present, and have ::widget_scroll() return a bool for 'handled', and have VteTerminal's GtkWidgetClass->scroll_event return FALSE for unhandled?
Comment 2 GNOME Infrastructure Team 2021-06-10 15:07:54 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/vte/-/issues/2251.