T O P I C R E V I E W |
gbozoki |
Posted - Feb 18 2011 : 11:23:17 PM Hi,
I just recently upgraded from 1827 to 1842 and noticed that the behavior of {...} changed. Using VS 2008 and C#. Earlier, when typing { I got this:
{
....|
}
but in 1842, I get this:
{
|}
Notice how the caret is now in front of the closing brace, not at the end of the middle line. Is there a setting to control this behavior? This is a very annyoing problem for me, I have to now correct almost every block of code I write because I start typing at the wrong position.
I have the default definition of {...} in the VA Snippets window. Here's my system info:
quote: VA_X.dll file version 10.6.1842.0 built 2011.02.03 Licensed to: VA X: <removed> (1-user license) Support ends 2012.02.12 DevEnv.exe version 9.0.30729.1 Enterprise msenv.dll version 9.0.30729.1 Font: Courier New 13(Pixels) Comctl32.dll version 6.0.2900.6028 Windows XP 5.1 Build 2600 Service Pack 3 2 processors (x86)
Platform: Win32 Stable Includes: c:\\Program Files\\Microsoft Visual Studio 9.0\\VC\\include; c:\\Program Files\\Microsoft Visual Studio 9.0\\VC\\atlmfc\\include; C:\\Program Files\\Microsoft SDKs\\Windows\\v6.0A\\include; C:\\Program Files\\Microsoft SDKs\\Windows\\v6.0A\\include;
Other Includes:
Stable Source Directories: c:\\Program Files\\Microsoft Visual Studio 9.0\\VC\\atlmfc\\src\\mfc; c:\\Program Files\\Microsoft Visual Studio 9.0\\VC\\atlmfc\\src\\mfcm; c:\\Program Files\\Microsoft Visual Studio 9.0\\VC\\atlmfc\\src\\atl; c:\\Program Files\\Microsoft Visual Studio 9.0\\VC\\crt\\src;
Thanks for any info. |
8 L A T E S T R E P L I E S (Newest First) |
support |
Posted - Mar 17 2011 : 11:56:38 PM case=55483 is fixed in build 1845 |
feline |
Posted - Feb 24 2011 : 1:52:51 PM I don't currently have an estimate for this, but it is being looked at. We try to fix regressions in the next build, since clearly regressions are bad. It really depends on the cause of the problem. Sorry to be so vague, but I am sure you understand that these things are sometimes tricky. |
gbozoki |
Posted - Feb 23 2011 : 10:41:19 PM feline,
Thanks for the info. I do have Indent=Block - my first post mistakenly shows the indent positions in the second case. This is what I have:
{
|}
(I edited the first post to correct it.)
I'll try with smart indenting but I still hope you guys can fix this soon. Do you have any rough ETA? |
feline |
Posted - Feb 23 2011 : 5:20:06 PM I have the settings files, thank you for this. I have reproduced the problem here, and found the trigger:
case=55483
For me this only happens if you have set:
IDE tools menu -> Options -> Text Editor -> C# -> Tabs -> Indenting = Block
If I set indenting to Smart then the problem does not show up. So you may want to try this work around for now. Alternatively, VA 1830 is the last build for me without this problem, the regression was introduced, by accident, in VA 1831.
http://www.wholetomato.com/support/history.asp
From your first post it looks like you have Indenting = Smart, since with block indenting, and simply tying { to insert both { and } into the code file, the caret will not be indented.
This also explains why editing the VA Snippet does not help, since this snippet is only used when surrounding code when pressing {, it is not used when simply typing { into the editor with nothing selected. |
gbozoki |
Posted - Feb 23 2011 : 12:49:05 PM Sent the files you asked for. |
feline |
Posted - Feb 21 2011 : 5:15:27 PM Most odd, the caret is positioned in the same place in both VA 1827 and 1842 for me.
Can you please export your VA and IDE settings and send them to me, and also include your C# VA Snippet TPL file:
VA Options -> Performance -> Export Settings IDE tools menu -> Import and Export Settings -> Export selected environment settings
The TPL file should be:
C:\\Documents and Settings\\ %USERNAME% \\Application Data\\VisualAssist\\Autotext\\cs.tpl
I can then import them here and see if I can reproduce the problem.
Please submit the files via the form:
http://www.wholetomato.com/support/contact.asp
including this thread ID or URL in the description, so we can match it up. |
gbozoki |
Posted - Feb 21 2011 : 12:17:22 PM feline,
Thanks for the reply - I see the problem in all C# files. This started right after I installed 1842 in all files that I worked on. (At the moment, I only work with C# files, not C++.) It doesn't seem like a content-related issue to me - in any file and using any code construct, I get the same behavior. (It happens simply when I type '{'.)
Note, that the closing brace is in the correct indentation level, not off by 1 character as in my example - that's because of the '|' character for the caret. So my problem is with the caret placement.
I tried changing how the {...} snippet is set up by adding/moving around $end$ but it doesn't seem to help. I also tried cleaning all VA data and reparsing everything but it didn't have an effect.
This snippet:
{$end$
....$selected$
}
gives me the same behavior, so moving $end$ around doesn't seem to have the expected effect. In this case, I'd expect this:
{|
....
} but I still get
{
|}
Hope this helps - I'd really like to get this fixed, I'm considering going back to 1827 because this really slows me down. |
feline |
Posted - Feb 21 2011 : 11:57:16 AM So far I cannot reproduce this problem here. I have just tried both VA 1827 and VA 1842 in VS2008 on the same machine, and I am getting the same behaviour and caret position with both versions.
Are you seeing this problem in all code files? Or only some code files?
Do you see this problem in a new C# code file? |
|
|