|
|
|
Ilya,
In response to your first question: I have 3 LCDs, 1280x1024, 1680x1050, 1280x1024. The middle monitor is widescreen. Generally I only need to see 2 docs at a time (unit test, and the class I'm testing). So I leave the middle monitor to display the 2 code windows, using 2 vertical tab groups. On the right edge of my left monitor I have the solution explorer, and on the left edge of the right monitor I have File Structure. I tend to pull out some other windows (output, errors, unit tester etc) and arrange them on the periphery. I've dropped the font size to 8 to get enough side by side realestate. I don't maximize VS, I just size it manually across multiple monitors. As for what I use FileStructure for. I like to refactor code a lot, and write short methods. As a result, the methods wind up being fairly numerous, and they tend to wind up fairly unorganized. I use filestructure to drag and drop them, and then to surround them w/ regions. Then, yes, I definitely use them to navigate around the document. The reason I'd like to have 2 is that I don't tend to write tests first (bad me), and so I like to see the code I'm testing, and it's structure so I can ensure that I'm testing it as thoroughly as possible. Jeff,
Thanks for your detailed response, it is very interesting and important to learn about various specific user scenarios. We will consider many-screens cases as yours, and probably multiply code structure windows in future versions. |
|||||||||||||||||||||||||||||||||||||||||||||||||
1. Too much screen real estate is used for each File Structure View. Even one often is too much.
2. Implies MDI mode or split groups. As code windows cannot be moved to secondary monitors, it's even less space for source code.
Also, what are using File Structure view for? Do you use Go to File Member feature for navigation?