Funny, I did a quick search, decided I would post something to
stackoverflow and would take a screenshot. Snaggit opened it on another
monitor. I could SEE the breakpoint column clearly in the screenshot!! So I
moved VS to that monitor and could see it. Seems my main monitor saturation
level was up higher (it's brightness didn't match my other two) and so the
default colour and the white background colour blend together so much that
I can't tell them apart.
Yep, just tested that theory, dropped contrast down (it was at 100% for
some reason) and I can see it now.
Anyway, another search to identify its name ("Indicator Margin") and I've
customised it to be much darker so there's no more missing it even with
higher contrast.It's mildly amusing how long you often put up with something before the "annoyedness" prompts some research (which is often a simple fix)! thanks for the reply... :) On Thu, Aug 1, 2013 at 9:06 AM, mike smith <[email protected]> wrote: > On Thu, Aug 1, 2013 at 11:01 AM, Stephen Price > <[email protected]>wrote: > >> I used to click the left margin to set a breakpoint. These days I have to >> guess click three to five times on average to hit the right spot, the >> column is much wider now. VS2012. >> >> Anyone else find this? Why is my left margin so wide now? Is it Resharper >> or some setting somewhere? The line numbers? The theme (modified light >> theme) If I remember I'm going to have problems I often click the line and >> hit F9 but it bugs me that I have to alter my "normal" habit to set >> breakpoints with one mouse click. >> > > Not for me, seems happy to set breakpoints anywhere on the grey bit. With > a proviso: If VS is busy doing stuff, it's not very responsive. (busy > with intellisense, compiling, whatever) > > -- > Meski > > http://courteous.ly/aAOZcv > > "Going to Starbucks for coffee is like going to prison for sex. Sure, > you'll get it, but it's going to be rough" - Adam Hills >
