
It also seems like a good reason to use Word Wrap. That doesn't seem unreasonable to me - in fact, I often do that in emacs, although I find the VS implementation too cumbersome to use.
#Msew program code
Yes, Uniwares, you are overreacting! msew said that he had two source code windows side-by-side.
#Msew program how to
I still expect that people know how to use a scroll bar, or type Ctrl+PgDn. Then you'll never ever need to word wrap any code.īut probably its now just me overreacting. It's not a troll if it's a valid point, I'm not making anything up here but trying to bring a major problem to attention, there are many others who installed VA X, wrote 15" and use a resolution > 800圆00. Zen is the art of being at one with the two'ness it is only with VA that i am prepared to use the VS editor. as for this tool, when i first started using VS i refused to use its editor, and did all of my editing in Vim for windows. i have never used word wrap in Vim, so i am not missing it in VS. I agree it's bad to have to choose between Word Wrap and Visual Assist, but VA definitely wins.Īs for work wrap, i am moving from Vim under Unix (via a dumb terminal) to VS + VAX under windows. something I can't believe they would do considering it makes writing OO code impossible. How is anyone expected to use a plugin like this? With bugs like this it renders VC++ totally unusable & disabled the beta, then today I found out they planned to charge money for this thing. WordWrap already had to be disabled in Visual Assist. I would like to see it fixed too, but my understanding from thread 416 is that it won't happen. Winner: ClickZ's Best Web Analytics Tool 2003 & 2004 Most people probably don't know that though, and unlike my original bug in 407, it's not obvious that this bug is anything to do with Word wrap. I know that VA doesn't work with Word wrap ( 407, 416). It turns out that they only happen if "Word wrap" is enabled. Having seen two of msew's "jump to end of line" bugs ( 1571 and this one) in quick succession, although I'd never seen them before, I started thinking what I'd changed. What keyboard mapping scheme is selected in Tools|Options|Environment|Keyboard? Does the problem remain if you switch temporarly to a default scheme? NET 2003\\Vc7\\atlmfc\\src\\atl Ĭ:\\Program Files\\Microsoft Visual Studio. NET 2003\\Vc7\\atlmfc\\src\\mfc Ĭ:\\Program Files\\Microsoft Visual Studio. NET 2003\\SDK\\v1.1\\include Ĭ:\\depot_vanguard\\coding\\source\\xlib\\boost\\boost Ĭ:\\Program Files\\Microsoft Visual Studio. NET 2003\\Vc7\\PlatformSDK\\include Ĭ:\\Program Files\\Microsoft Visual Studio. NET 2003\\Vc7\\PlatformSDK\\include\\prerelease Ĭ:\\Program Files\\Microsoft Visual Studio. NET 2003\\Vc7\\atlmfc\\include Ĭ:\\Program Files\\Microsoft Visual Studio. NET 2003\\Vc7\\include Ĭ:\\Program Files\\Microsoft Visual Studio. Is there some option to turn this behavior off or this a bug?Ĭ:\\Program Files\\Microsoft Visual Studio. Your cursor will end up at end of the line after the Void someNameSpace::someClass:someFunc( someClass* p_someData )Īnd type either.

You have have a class with a private impl struct. or ->Ĭursor jumps to end of line when adding a.
#Msew program software
Whole Tomato Software Forums - cursor jumps to end of line when adding a.
