Bug 10838 - Xamarin Studio 4.0 - tabs don't respond to clicks
Summary: Xamarin Studio 4.0 - tabs don't respond to clicks
Status: RESOLVED DUPLICATE of bug 10790
Alias: None
Product: Android
Classification: Xamarin
Component: General ()
Version: 4.8.x
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2013-03-01 20:43 UTC by Ed Cavazos
Modified: 2013-03-01 21:04 UTC (History)
1 user (show)

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


Attachments
Xamarin Studio tabs bug (79.00 KB, image/png)
2013-03-01 20:43 UTC, Ed Cavazos
Details


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:
Status:
RESOLVED DUPLICATE of bug 10790

Description Ed Cavazos 2013-03-01 20:43:20 UTC
See the attached screenshot. I open a few files so that various tabs are displayed. On numerous occasions the tabs have become unresponsive to clicks. I can still close the files via File -> Close. I can also switch to them using the Solution window.

This is on a Windows 7 64-bit system.
Comment 1 Ed Cavazos 2013-03-01 20:43:59 UTC
Created attachment 3525 [details]
Xamarin Studio tabs bug
Comment 2 Mikayla Hutchinson [MSFT] 2013-03-01 21:04:37 UTC

*** This bug has been marked as a duplicate of bug 10790 ***