Answered by:
Editing a post corrupts the code window

Question
-
Attempting to edit the below post for a spelling mistake in the text removed the newlines from the code in the code pane. Then, attempting to post the code outside the code pane so that OP had some chance of reading it created a complete mess whereever the constructs
<vbfixedstring(10)>Public INV_NO As String
or
<vbfixedarray(19)>Public ID() As String
were used.This is valid VB syntax, but the editor can't handle it. It doubles them up and inserts '/' and then dulpicates the whole thing.
Answers
-
Yeah, three are a few bugs around edit and resubmission of code that this might happen to. We are working on it. Is this what you want it to look like?
Let me know and I'll go in and fix that (or try to).
Community Forums Program Manager
- Proposed as answer by Ed Price - MSFTMicrosoft employee Wednesday, February 15, 2012 6:37 PM
- Marked as answer by Ed Price - MSFTMicrosoft employee Thursday, March 15, 2012 3:04 AM
-
I have used your example to update the original post and it now looks OK.
The editing problems appear to be associated with the delay in the edit window becoming active. I have made these changes on a machine with W7 and IE8 and things are working a little better. The original machine was Vista and IE8 and it is now quite unusable for MSDN newsgroups. This one isn't great, but at least I can get the caret in the edit window within two or three attempts.
EDIT: Pkease ignore the comment about W7/Vista - I made that change at about the same time that the latest changes went in. Performance with both machines is essentially the same: somewhat better than it was immediately after the upgrade, but still worse than the previous version.- Edited by Acamar Sunday, February 12, 2012 5:47 AM Update
- Proposed as answer by Ed Price - MSFTMicrosoft employee Wednesday, February 15, 2012 6:37 PM
- Marked as answer by Ed Price - MSFTMicrosoft employee Thursday, March 15, 2012 3:04 AM
All replies
-
Yeah, three are a few bugs around edit and resubmission of code that this might happen to. We are working on it. Is this what you want it to look like?
Let me know and I'll go in and fix that (or try to).
Community Forums Program Manager
- Proposed as answer by Ed Price - MSFTMicrosoft employee Wednesday, February 15, 2012 6:37 PM
- Marked as answer by Ed Price - MSFTMicrosoft employee Thursday, March 15, 2012 3:04 AM
-
I have used your example to update the original post and it now looks OK.
The editing problems appear to be associated with the delay in the edit window becoming active. I have made these changes on a machine with W7 and IE8 and things are working a little better. The original machine was Vista and IE8 and it is now quite unusable for MSDN newsgroups. This one isn't great, but at least I can get the caret in the edit window within two or three attempts.
EDIT: Pkease ignore the comment about W7/Vista - I made that change at about the same time that the latest changes went in. Performance with both machines is essentially the same: somewhat better than it was immediately after the upgrade, but still worse than the previous version.- Edited by Acamar Sunday, February 12, 2012 5:47 AM Update
- Proposed as answer by Ed Price - MSFTMicrosoft employee Wednesday, February 15, 2012 6:37 PM
- Marked as answer by Ed Price - MSFTMicrosoft employee Thursday, March 15, 2012 3:04 AM
-
Replace Old and Faulty Hardware Components. Hardware components have to work properly for the normal functioning of the computer.
Backup the Dta Regularly.
Be Vigilant Against Virus Attacks.
Check Hard Disk Health Regularly.
Recover lost data using Windows recovery tools.Hope This Works,
Peter