Bug 2836 - disable alt+scroll in pads
Summary: disable alt+scroll in pads
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: unspecified
Hardware: Macintosh Mac OS
: Low normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2012-01-10 13:39 UTC by ajb
Modified: 2013-12-05 18:34 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description ajb 2012-01-10 13:39:44 UTC
This is desired behavior for allowing users to resize text in the editor but should not be allowed for pads. There ought to be a stepped magnification menu option for adjusting the text size in pads globally (or with more granular options for specific pads)

Obviously a low priority. But it can be an annoying little quirk when you run across it :-)
Comment 1 Mikayla Hutchinson [MSFT] 2012-01-10 14:28:50 UTC
There is a global setting for the pad font, which includes font size. The granular setting is the zoom. Why should it not be allowed for pads?
Comment 2 Mikayla Hutchinson [MSFT] 2012-04-25 12:32:46 UTC
Does this feature cause a problem? Why should we remove it?
Comment 3 PJ 2013-11-19 17:04:39 UTC
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?

If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
Comment 4 PJ 2013-12-05 18:34:48 UTC
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.

Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.