Bug 12024 - Breakpoints window scrolls on enable/disable
Summary: Breakpoints window scrolls on enable/disable
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger ()
Version: 4.0.3
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Jeffrey Stedfast
URL:
Depends on:
Blocks:
 
Reported: 2013-04-29 11:07 UTC by Chris Hamons
Modified: 2013-04-29 14:46 UTC (History)
1 user (show)

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


Attachments
Image (73.83 KB, image/png)
2013-04-29 11:07 UTC, Chris Hamons
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 FIXED

Description Chris Hamons 2013-04-29 11:07:44 UTC
Created attachment 3890 [details]
Image

I have a set of breakpoints with some enabled and disabled. When I enable or disable anything except the top one, the entire pane flickers and scrolls. (See attached image). 

(Also see the strange scroll bar bug).
Comment 1 Jeffrey Stedfast 2013-04-29 14:46:53 UTC
The problem was that we were clearing & regenerating the list whenever the breakpoint store changed (which enabling/disabling causes). The fix was to disconnect the changed event from the backend since we were handling the enable/disable in the UI.

Thanks for reporting this!