Common Editor Issues in VS 2010 Beta1

Common Editor Issues in VS 2010 Beta1 | Microsoft Share Point

Common Editor Issues in VS 2010 Beta1 | Microsoft Share Point — Tue, 02 Jun 2009 20:42:29 GMT

PingBack from http://microsoft-sharepoint.simplynetdev.com/common-editor-issues-in-vs-2010-beta1/

re: Common Editor Issues in VS 2010 Beta1

Joku — Wed, 03 Jun 2009 16:59:40 GMT

Or you could make it have some fade or timer so that it wouldn't flicker if you are moving mouse over it... Isn't the editor WPF? This kind of thing was supposed to be trivial.

re: Common Editor Issues in VS 2010 Beta1

VSEditor — Wed, 03 Jun 2009 23:40:27 GMT

Joku -

That's another possibility we're considering. It isn't technically difficult, but there's a usability tradeoff between:

1.) The highlight responding immediately (as in Beta1) and causing some flicker when mousing over the outlining margin quickly to move the mouse somewhere else, e.g. the toolbox, and

2.) The highlight fading in or waiting for a short time and feeling slow or unresponsive when you hover over the outlining margin intentionally.

While we don't have a definitive answer yet, we're working to find a solution that strikes the right balance.

- Brittany

re: Common Editor Issues in VS 2010 Beta1

adi hodos — Tue, 09 Jun 2009 13:21:14 GMT

Are there any plans to support custom code styles for native code ? For example NetBeans CPP pack and Eclipse CDT allow many customizations ( spaces before parenthesis , after comma , identation of preprocessor directives , every function parameter on a new line to name only a few ). I would very much like to see options like those available in Visual Studio also.

re: Common Editor Issues in VS 2010 Beta1

VSEditor — Wed, 10 Jun 2009 23:40:37 GMT

adi hodos -

Options for formatting code are provided by each language team, so some languages have a richer set of style choices than others. For example, you'll see a wide variety of customizations available under Tools->Options->Text Editor-> C#->Formatting, including several of the ones you mention and many more.

Unfortunately, C/C++ does not offer as many choices for formatting native code. I agree that this is an area that could be improved, but it falls outside of the Editor team's control, and I don't believe the C/C++ team is planning significant changes in formatting options for VS 2010.

- Brittany

re: Common Editor Issues in VS 2010 Beta1

adi hodos — Thu, 11 Jun 2009 18:33:46 GMT

I'm sorry to hear that , because if you're writing native code and you want to use a different formatting style sometimes it feels like the editor is working against you :)

re: Common Editor Issues in VS 2010 Beta1

Pete — Sun, 21 Jun 2009 22:07:01 GMT

I've had a constand editor problem where the screen takes forever to render. I've been up and down the tree trying to find the answer.

Your post spoke of issues with fonts being incorreclty chosen or going back to the wrong ones. I kept noticing drive activity sometime 5 minutes or more.

The fix to my problem appears to be simple, I switched to Mariam Fixed from Consolas. Now it runs like my quad core should run. I actually think that this could be from NOT VS 2005, 2008 or 2010 issue but more likely that my font catalog is quite large since I also run Photoshop. I suspect that maybe a few of the FreeWare fonts are the culprits.

Whats in the Fonts Folder could be why the editor runs slow. I am installing a font manager but my extremely slow rendering seems. There are days just going from code to HTML to splut could take 20 seconds. For me this was adding up to hours.

Please load fonts in, fill that folder up and you might see the same results. A font Manager should solve this issues.

Pete@petebennett.net

re: Common Editor Issues in VS 2010 Beta1

Pete Bennett — Sun, 21 Jun 2009 22:16:09 GMT

A visual challenge that would help is as follows:

Create Editor Feature: Allow for highlighting a region, setting a solid color similar to when you hold the mouse over the regions area. Make it permanent so that when scrolling through lots of HTML or Code, you can quickly skip to or skip over backgrounds that colored code.

The main advantage is you dont have to read everything, this would a great features behind comments, then we create SOLID bars, backgrounds and regions. You look for the colors not the code.

You would amazed on how much effort is spent reading code when drilling down. Even some symbols, stars, that could be anchored on the left bar, similar to breakpoints but it should traverse from left to right or edge to edge.

Just like the box above this comment box would be so helpful and cut down on reading text.

Want a sample? Let me know.