T
Tom Dacon
One thing that drives me nuts about coding in VB.Net is the behavior of the
IDE when you split the code window in two by dragging down the separator at
the top of the vertical scroll bar. If you have regions defined in the
source file, splitting the window causes the regions to collapse. If you've
got a region open and are somewhere within it, and then decide to split the
window to look at something elsewhere in the file, pulling the code window
splitter down causes all regions to collapse in both subwindows and you lose
your place in the file. I can't find anything in the VB options that seems
to offer any control over this. Has anyone else been bothered enough by this
to find a solution?
I always tell people that I'm equally comfortable in VB.Net and C#, and I am
as far as writing code goes, but whenever I start a new project of my own I
almost always do it in C#, just because of this seemingly minor irritation.
Thanks for listening,
Tom Dacon
Dacon Software Consulting
IDE when you split the code window in two by dragging down the separator at
the top of the vertical scroll bar. If you have regions defined in the
source file, splitting the window causes the regions to collapse. If you've
got a region open and are somewhere within it, and then decide to split the
window to look at something elsewhere in the file, pulling the code window
splitter down causes all regions to collapse in both subwindows and you lose
your place in the file. I can't find anything in the VB options that seems
to offer any control over this. Has anyone else been bothered enough by this
to find a solution?
I always tell people that I'm equally comfortable in VB.Net and C#, and I am
as far as writing code goes, but whenever I start a new project of my own I
almost always do it in C#, just because of this seemingly minor irritation.
Thanks for listening,
Tom Dacon
Dacon Software Consulting