Disabled Undo - argh!
-
Ok, I'm sure that Ctrl-Z is one of the most used keyboard shortcuts the world over. Undo, is possibly one of the most important features in any text editor - certainly in an IDE. Why is it then, that VS.NET keeps deciding to completely disable Undo and Redo - everything greyed out, keyboard shortcuts don't work. The only way to recover is to exit and reload VS.NET. Anyone else experience this problem or even have a solution? thanks, -- Simon Steele Programmers Notepad - http://www.pnotepad.org/
-
Ok, I'm sure that Ctrl-Z is one of the most used keyboard shortcuts the world over. Undo, is possibly one of the most important features in any text editor - certainly in an IDE. Why is it then, that VS.NET keeps deciding to completely disable Undo and Redo - everything greyed out, keyboard shortcuts don't work. The only way to recover is to exit and reload VS.NET. Anyone else experience this problem or even have a solution? thanks, -- Simon Steele Programmers Notepad - http://www.pnotepad.org/
Yea, I've seen it a few times as well. Overall I get the feeling that VS.NET was not quite past beta. Even with SP2 I still have a number of frustrations with the product - like unpinned windows getting stuck closed. It took me almost a week to get the Memory windows back. But, this is MS. Deliver, deliver, deliver and let the buyer beware.
-
Yea, I've seen it a few times as well. Overall I get the feeling that VS.NET was not quite past beta. Even with SP2 I still have a number of frustrations with the product - like unpinned windows getting stuck closed. It took me almost a week to get the Memory windows back. But, this is MS. Deliver, deliver, deliver and let the buyer beware.
David Viggiano wrote: Even with SP2 As these are only framework service packs they sure won't help on IDE matters. I never experienced *this* problem by the way but some other very weird things.... Cheers Martin "Situation normal - all fu***d up" Illuminatus!
-
Yea, I've seen it a few times as well. Overall I get the feeling that VS.NET was not quite past beta. Even with SP2 I still have a number of frustrations with the product - like unpinned windows getting stuck closed. It took me almost a week to get the Memory windows back. But, this is MS. Deliver, deliver, deliver and let the buyer beware.
For such a complex product, and given that VS.NET was a brand new IDE, I would have expected at least three betas from MS before releasing it (instead of the two plus a brief RC). I expected that the IDE would be buggy. I remember that the first version of VC++ Developer Studio (VC++ 4) was quite buggy. The next version was much more stable. As was VC++ 6. Much simpler products, such as the Opera web browser, routinely have several betas, e.g., up to 5. BTW, .NET SP2 only fixes .NET, not the IDE. I get the impression that there won't be an SP for VS. It will be rolled into the impending 1.1 upgrade. Nonetheless I don't think MS is especially bad on buggy releases. Everyone else seems just as bad. It's a perennial industry problem. Kevin
-
For such a complex product, and given that VS.NET was a brand new IDE, I would have expected at least three betas from MS before releasing it (instead of the two plus a brief RC). I expected that the IDE would be buggy. I remember that the first version of VC++ Developer Studio (VC++ 4) was quite buggy. The next version was much more stable. As was VC++ 6. Much simpler products, such as the Opera web browser, routinely have several betas, e.g., up to 5. BTW, .NET SP2 only fixes .NET, not the IDE. I get the impression that there won't be an SP for VS. It will be rolled into the impending 1.1 upgrade. Nonetheless I don't think MS is especially bad on buggy releases. Everyone else seems just as bad. It's a perennial industry problem. Kevin
Kevin McFarlane wrote: I get the impression that there won't be an SP for VS. It will be rolled into the impending 1.1 upgrade. I heard somewhere (maybe here on CP?) that ms will release a service pack around the time of the everett release for those who don't want to upgrade. But I don't know if this information is still valid... Cheers Martin "Situation normal - all fu***d up" Illuminatus!
-
Ok, I'm sure that Ctrl-Z is one of the most used keyboard shortcuts the world over. Undo, is possibly one of the most important features in any text editor - certainly in an IDE. Why is it then, that VS.NET keeps deciding to completely disable Undo and Redo - everything greyed out, keyboard shortcuts don't work. The only way to recover is to exit and reload VS.NET. Anyone else experience this problem or even have a solution? thanks, -- Simon Steele Programmers Notepad - http://www.pnotepad.org/
Simon Steele wrote: Why is it then, that VS.NET keeps deciding to completely disable Undo and Redo - everything greyed out, keyboard shortcuts don't work. The only way to recover is to exit and reload VS.NET. Anyone else experience this problem or even have a solution? You scare me. Up until I read your post the other day VS.NET was doing ok for me (some bugs, but not what you are experiencing.) Then yesterday I hit Ctrl-Z and VS.NET displays an error saying "Unable to Undo/Redo." Odd I thought. Then suddenly syntax colouring stops working and intellisense fails. Then when I compile it compiles fine, even with obvious bugs in the syntax... I saved all, closed, restarted and it is all working fine now... I think my VS.NET had a chat with yours :-D
Paul Watson
Bluegrass
Cape Town, South AfricaRay Cassick wrote:
Well I am not female, not gay and I am not Paul Watson -
Simon Steele wrote: Why is it then, that VS.NET keeps deciding to completely disable Undo and Redo - everything greyed out, keyboard shortcuts don't work. The only way to recover is to exit and reload VS.NET. Anyone else experience this problem or even have a solution? You scare me. Up until I read your post the other day VS.NET was doing ok for me (some bugs, but not what you are experiencing.) Then yesterday I hit Ctrl-Z and VS.NET displays an error saying "Unable to Undo/Redo." Odd I thought. Then suddenly syntax colouring stops working and intellisense fails. Then when I compile it compiles fine, even with obvious bugs in the syntax... I saved all, closed, restarted and it is all working fine now... I think my VS.NET had a chat with yours :-D
Paul Watson
Bluegrass
Cape Town, South AfricaRay Cassick wrote:
Well I am not female, not gay and I am not Paul WatsonPaul Watson wrote: "Unable to Undo/Redo." At least you were told!! Mine just disables the menu item and that's it. I wonder if there's some magical automation way of re-enabling the undo system - I'm sure it must be accessable through the VS.NET object model. Anyone got any ideas? Roll on SP-1. -- Simon Steele Programmers Notepad - http://www.pnotepad.org/
-
Kevin McFarlane wrote: I get the impression that there won't be an SP for VS. It will be rolled into the impending 1.1 upgrade. I heard somewhere (maybe here on CP?) that ms will release a service pack around the time of the everett release for those who don't want to upgrade. But I don't know if this information is still valid... Cheers Martin "Situation normal - all fu***d up" Illuminatus!
-
Ok, I'm sure that Ctrl-Z is one of the most used keyboard shortcuts the world over. Undo, is possibly one of the most important features in any text editor - certainly in an IDE. Why is it then, that VS.NET keeps deciding to completely disable Undo and Redo - everything greyed out, keyboard shortcuts don't work. The only way to recover is to exit and reload VS.NET. Anyone else experience this problem or even have a solution? thanks, -- Simon Steele Programmers Notepad - http://www.pnotepad.org/
while (IDE_Acts_Weird()) {
Exit_IDE();
DeleteFile("*.ncb");
DeleteFile("*.aps");
Start_IDE();
}
Software Zen:
delete this; -
while (IDE_Acts_Weird()) {
Exit_IDE();
DeleteFile("*.ncb");
DeleteFile("*.aps");
Start_IDE();
}
Software Zen:
delete this;