By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
431,934 Members | 1,692 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 431,934 IT Pros & Developers. It's quick & easy.

Immediate Window annoyance

P: n/a
I am using the Immediate Window a lot to see the progress of the
application. In VS2003, if your cursor was at the very bottom, the
window would scroll down whenever something new showed up. If your
cursor was somewhere in the middle of the text output, then there would
be no scrolling.

In VS2005, the Immediate Window scrolls regardless of where the cursor
is which is very annoying. Sometimes you want to go back up in the
window to check something that happened earlier. But if something shows
up in the window at that time, the cursor will just jump to the bottom
of the screen.

Is there some kind of tweak, hack, setting, whatever to make VS2005
Immediate Window work like it did in VS2003?

Thanks
Apr 13 '07 #1
Share this Question
Share on Google+
6 Replies


P: n/a
Hi Frank,

I am sorry that I may not understand your scenario exactly.
>In VS2003, if your cursor was at the very bottom, the window would scroll
down whenever something new showed up.

When we debug a program with VS debugger, we could input some commands in
the Immediate window and press the Enter key to check something. Could you
tell me what you mean by the "something new showed up" in the above
sentence?

Could you please explain more in detail on how you use the Immediate window
in both VS.NET 2003 and VS 2005 when debugging the application?

Only if I understand your scenario, I could provide you with possible
assistance.

Thank you for your understanding and cooperation!
Sincerely,
Linda Liu
Microsoft Online Community Support

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

Apr 16 '07 #2

P: n/a
Linda Liu [MSFT] wrote:
Hi Frank,

I am sorry that I may not understand your scenario exactly.
>In VS2003, if your cursor was at the very bottom, the window would scroll
down whenever something new showed up.

When we debug a program with VS debugger, we could input some commands in
the Immediate window and press the Enter key to check something. Could you
tell me what you mean by the "something new showed up" in the above
sentence?
Imagine code like below.

for (int i = 0; i < 10000000; i++)
{
Console.WriteLine (i.ToString());
Thread.Sleep(100);
}

We all agree that the loop would take a long time to finish.

In VS2005, while the app is running, if you want to go scroll back up in
the window, you can't. Because the next Console.WriteLine executes, the
window will scroll down automatically to the very last entry.

In VS2003, as long as the cursor is not on the very last line (e.g. you
clicked elsewhere in the Immediate Window), the window will not
automatically scroll down when Console.WriteLine executes, allowing you
to inspect the contents of the Immediate Window in peace.

Regards
>
Could you please explain more in detail on how you use the Immediate window
in both VS.NET 2003 and VS 2005 when debugging the application?

Only if I understand your scenario, I could provide you with possible
assistance.

Thank you for your understanding and cooperation!
Sincerely,
Linda Liu
Microsoft Online Community Support
Apr 17 '07 #3

P: n/a
Hi Frank,

Thank you for your reply.

I have pasted your sample code in a form's Load event handler within my
test WinForm application.

When the application is run, I see the values of the variable 'i' are
printed in the Output window. The Immediate window has no output.

Is there any difference between your project and mine?

Sincerely,
Linda Liu
Microsoft Online Community Support

Apr 18 '07 #4

P: n/a
Linda Liu [MSFT] wrote:
Hi Frank,

Thank you for your reply.

I have pasted your sample code in a form's Load event handler within my
test WinForm application
When the application is run, I see the values of the variable 'i' are
printed in the Output window. The Immediate window has no output.
Is there any difference between your project and mine?

I am sorry, I dropped the ball. Replace the Console.WriteLine() with
System.Diagnostics.Debug.WriteLine(). So the code goes like this:
using System.Diagnostics;

for (int i = 0; i < 10000000; i++)
{
Debug.WriteLine (i.ToString());
Thread.Sleep(100);
}

Apr 18 '07 #5

P: n/a
Hi Frank,

Thank you for your prompt response.

I found an debugging setting of 'Redirect all Output Window text to the
Immediate Window' in VS05 and after I turn on this option, I saw the values
of the variable 'i' are printed to the Immediate window.

I did see that the Immediate window scrolls regardless of where the cursor
is whenever something new shows up.

I haven't found a setting to change the above behavior of the Immediate
window.

But this problem doesn't exit in the Output window, so I suggest you use
Output window instead of the Immediate window.

To do this, go to the menu Tools | Options. In the Options window, navigate
to Debugging | General. On the right hand, find the option of 'Redirect all
Output Window text to the Immediate Window' and clear the checkbox before
it.

Hope this helps.

Sincerely,
Linda Liu
Microsoft Online Community Support

Apr 19 '07 #6

P: n/a
Linda,

Thank you very much. This did the trick. It now works as I expect it.

Regards
Linda Liu [MSFT] wrote:
Hi Frank,

Thank you for your prompt response.

I found an debugging setting of 'Redirect all Output Window text to the
Immediate Window' in VS05 and after I turn on this option, I saw the values
of the variable 'i' are printed to the Immediate window.

I did see that the Immediate window scrolls regardless of where the cursor
is whenever something new shows up.

I haven't found a setting to change the above behavior of the Immediate
window.

But this problem doesn't exit in the Output window, so I suggest you use
Output window instead of the Immediate window.

To do this, go to the menu Tools | Options. In the Options window, navigate
to Debugging | General. On the right hand, find the option of 'Redirect all
Output Window text to the Immediate Window' and clear the checkbox before
it.

Hope this helps.

Sincerely,
Linda Liu
Microsoft Online Community Support
Apr 19 '07 #7

This discussion thread is closed

Replies have been disabled for this discussion.