Currently, Quick Find, unlike for example Find in Firefox, moves the scroll position on the page as soon as you start erasing what you searched for, instead of keeping you at the same place. Also, when you reach the last found item and press enter, it first pops up a very annoying modal dialog instead of behaving more reasonably such as just writing that "no more items were found" in the blue status bar and then wrapping around to the first found item on the page, and then if you press enter again after dismissing the modal, it starts inserting carriage returns in the page. What sort of a person wants this sort of behaviour, wherein you get switched without clear warning from searching for text to accidentally editing it? I certainly don't want this sort of behaviour from a text editor.

In summary, please make Quick Find less annoying by getting it to wrap around or stop when it reaches the end, and without popping up a modal dialog, and without switching focus to editing.

I use Spy++ a lot especially when I make a customized widget.

However, I noticed that the tool is not updated for long time. (I've written Win32 code from 1990. )

So, here are some enhancement which will help people a lot.

1. Visual bookmark or separator on the message list.
When you move your mouse or type something on a widget which is captured or being monitored, Spy++ will show what messages are generated. There, you can have interest messages at specific location. So, if a user can set a visual mark, it would be helpful.

2. Search & highlight window messages
On the message list mentioned above, it would be great if window messages can be searchable and highlight all matching text. For example, if you type EM_GETSEL, searches any lines with EM_GETSEL and highlight all the instances of EM_GETSEL in the list.

3. On the message tab on Logging Options, It would be great if Messages to View list only shows only those messages selected in the Message Groups. So, there should be also select all and clear all of the Message Groups also.

4. On the Messages to View, it would be great if 'searching' is possible.

5. On the Messages to View list, please group messages by each item on the Message Groups.

The fact that ProcessStartInfo.Arguments is a string is a major design mistake; it should have been an array. By making it a string, anyone who wants to pass arbitrary filenames to another process has to go through an error-prone process of quoting those filenames to make sure they don't contain spaces, or quote characters, or other characters that could be misinterpreted. There are many, MANY ways to get this wrong, and a quick Google search on the Internet will find lots of advice (and sample code) on how to quote your arguments -- and most of it is WRONG, and will cause bugs and/or security holes! (See http://gfxmonk.net/2014/04/25/escaping-an-array-of-command-line-arguments-in-csharp.html for the correct way to do it, by the way).

It would be much better if, like Python, the Arguments property had been made an array in the first place. Since it's probably impossible to undo that bad decision now, the next best thing is to create a new property called ArgumentsArray, and have the .NET library guarantee that any parameters in ArgumentsArray will be properly quoted so that the called process receives those arguments exactly as I passe them in. (So if I pass in an array containing the string "\"Don't give up!\", the programmer said." and nothing else, then that's exactly what the new process will receive: an array with one string, which contains two quotation marks, one single quote, and some spaces.)

This has probably been a source of nasty bugs and programmer frustration for years, but it doesn't need to continue to be a source of bugs. There's probably no way to remove the broken Arguments property at this point given how much bad code has already been written to depend on it, but it *is* possible to create something that actually works correctly, so that one day the Arguments property can finally be deprecated.

Hi there,
How are you?

I know you probably get lots of emails and don't have much time, Then I try to make it short.

Jumping right on the main point:
In the past, I had to understand a large code which I hadn't written myself and I didn't have access to the code developer. Totally it had around 20 functions and thousands of code lines. It was a really hard task and took a lot of my time. At that period I thought to myself If there was a fast way to find out how many functions are involved in the program and what their relation is, it would be really helpful and makes the work for me much easier.

A few days ago something came into my mind. I thought if you provide it in code editor environment, it can be very helpful and useful to a lot of people specially those working with large codes and people who have to figure out a code with lots of functions which has been previously written.

Here it is, we can provide a small window in the editor showing different functions as small rectangle and their relations as some arrows connecting the corresponding rectangles. For example (look at the attached picture), if scanner function has been called only through main function, there should be just one arrow connecting scanner function and main function. Judging similar to this, all other arrows are drawn. Apart from that, user should be able to navigate to different functions just by clicking on its rectangle in this window.
I have attached a pictures showing my idea.

I hope this is useful for you and you use it in your new IDE versions!

regards,

When loading or reloading a solution, there should be a modal dialog presented because it seems that the entire user-experience is blocked from interaction anyways.

When changing branches in Team Explorer, the solution automatically gets reloaded without any interaction from the user, but the Solution Explorer window isn't visible. This means the experience is a deadlocked Visual Studio window with obvious indication as to why.

Instead, a modal dialog should be presented to the user showing what is happening and the progress indicator made visible so that user has an idea how long a wait is in store - as an added bonus, there's room for a 'Cancel` button on the modal dialog.