{"id":225284,"date":"2010-06-21T15:47:37","date_gmt":"2010-06-21T22:47:37","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/visualstudio\/?p=225284"},"modified":"2019-05-03T15:52:57","modified_gmt":"2019-05-03T22:52:57","slug":"document-well-2010-plus-hidden-options","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/visualstudio\/document-well-2010-plus-hidden-options\/","title":{"rendered":"Document Well 2010 Plus: Hidden Options"},"content":{"rendered":"<p><span style=\"font-size: x-small;\"><span style=\"color: #666666;\">[<b>Update\n7\/20\/2010<\/b>]: Updated changes made for version 10.0.10710.22 of the Pro Power\nTools. Please take a look at the <a href=\"#changelog\">changelog<\/a>.<\/span><\/span><\/p>\n<p>A couple of posts ago I announced the availability of <a href=\"http:\/\/blogs.msdn.com\/b\/visualstudio\/archive\/2010\/06\/10\/document-well-2010-plus.aspx\">Document Well 2010 Plus<\/a> as part of the <a href=\"http:\/\/visualstudiogallery.msdn.microsoft.com\/en-us\/d0d33361-18e2-46c0-8ff2-4adea1e34fef\">Visual Studio 2010 Pro Power Tools<\/a>. Since then we have received lots of feedback about our extension, for which I am very grateful. User feedback has centered around two main points:<\/p>\n<ol>\n<li>There should be an option to hide the pin button<\/li>\n<li>When using custom colors for tabs, the selected tab is sometimes not clearly distinguishable<\/li>\n<\/ol>\n<p>Fortunately, the extension has a couple of hidden options that will let you alleviate these two points, as well as others that hopefully will help you in your daily work. During development of the extension we experimented internally with many different options for the features available in the extension. For the first release it was decided that exposing all options could be confusing and overwhelming to our users, and so the options dialog UI was simplified. You will find here all options that were hidden due to this simplification. I encourage you to try them out and let us know if you find them useful or not.<\/p>\n<ul>\n<li><a href=\"#pinnedtabsoptions\">Pinned Tabs Options<\/a>\n<ul>\n<li><a href=\"#pinbuttonvisibleinunpinnedtabs\">Pin button visible in unpinned tabs<\/a><\/li>\n<li><a href=\"#maintainpinnedstatus\">Maintain pinned status if document is removed from document well<\/a><\/li>\n<li><a href=\"#pinnedtabsappearinoriginalorder\">Pinned tabs appear in original order<\/a><\/li>\n<\/ul>\n<\/li>\n<li><a href=\"#tabpanelposition\">Tab Panel Position<\/a>\n<ul>\n<li><a href=\"#tabsonbottom\">Tabs on bottom of document well<\/a><\/li>\n<li><a href=\"#tabsonright\">Tabs on right of document well<\/a><\/li>\n<\/ul>\n<\/li>\n<li><a href=\"#coloroptions\">Color Options<\/a>\n<ul>\n<li><a href=\"#customcolorforselected\">Selected tab color options<\/a><\/li>\n<li><a href=\"#gradientsforcustom\">Use gradients for custom colors<\/a>\n<ul>\n<li><a href=\"#fadetodefault\">Custom color fades to default tab color<\/a><\/li>\n<li><a href=\"#fadetomoreintense\">Custom color fades to more intense tab color<\/a><\/li>\n<li><a href=\"#fadetolessintense\">Custom color fades to less intense tab color<\/a><\/li>\n<\/ul>\n<\/li>\n<li><a href=\"#regexprecedence\">Regular expression colors have precedence over project colors<\/a><\/li>\n<\/ul>\n<\/li>\n<li><a href=\"#regexoptions\">Regular Expression Options<\/a>\n<ul>\n<li>Use full document path for regular expression match<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<p><a name=\"pinnedtabsoptions\"><\/a><\/p>\n<h2>Pinned Tabs Options<\/h2>\n<p><a name=\"pinbuttonvisibleinunpinnedtabs\"><\/a><\/p>\n<h2>Pin button visible in unpinned tabs<\/h2>\n<p>This has been added to the options UI in our latest release.<\/p>\n<p><a name=\"maintainpinnedstatus\"><\/a><\/p>\n<h2>Maintain pinned status if document is removed from document well<\/h2>\n<p>By default, when a document is pinned and it is removed from the document well (by making it float or closing it) it loses its pinned status, and you will need to mark it as pinned again when you return it to the document well. Running the following command will maintain pinned status for documents that are floated or closed. Pinned status will only be removed if you manually unpin the tab.<\/p>\n<p><tt>reg add HKEY_CURRENT_USER\\Software\\Microsoft\\VisualStudio\\10.0\\DialogPage\\Microsoft.DocWellBehavior.GeneralOptions \/v IsPinStatusSticky \/t REG_SZ \/d True \/f<\/tt><\/p>\n<p>&nbsp;<\/p>\n<p><a name=\"pinnedtabsappearinoriginalorder\"><\/a><\/p>\n<h2>Pinned tabs appear in original order<\/h2>\n<p>By default, when you pin tabs they will be added to the pinned tabs group in the order in which they were pinned. Running the following command will make them appear in the order in which they originally appeared instead:<\/p>\n<p><tt>reg add HKEY_CURRENT_USER\\Software\\Microsoft\\VisualStudio\\10.0\\DialogPage\\Microsoft.DocWellBehavior.GeneralOptions \/v ArePinnedTabsInPinOrder \/t REG_SZ \/d False \/f<\/tt><\/p>\n<p>This might become more clear with an example. Say you had the following three tabs open:<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2019\/05\/6038.pinorder_originaltabs.png\" border=\"0\" \/><\/p>\n<p>By default, when you pin <tt>Class3.cs<\/tt>, then <tt>Class2.cs<\/tt>, then <tt>Class1.cs<\/tt>, they will appear in the order in which they were pinned, as shown here:<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2019\/05\/0005.pinorder_default.png\" border=\"0\" \/><\/p>\n<p>After running the above command and pinning the three tabs in the same order shown above, however, they will appear as follows, which is the same order in which they appeared originally:<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2019\/05\/3073.pinorder_keeporder.png\" border=\"0\" \/><\/p>\n<p><a name=\"tabpanelposition\"><\/a><\/p>\n<h2>Tab Panel Position<\/h2>\n<p>By default tabs appear on top of the document well. The options UI provides the ability to show tabs vertically, which positions them on the left of the well. Additionally, the extension has the ability to position tabs on the bottom and on the right of the document well.<\/p>\n<p><a name=\"tabsonbottom\"><\/a><\/p>\n<h2>Tabs on bottom of document well<\/h2>\n<p>Run the following command to position tabs on the bottom of the document well:<\/p>\n<p><tt>reg add HKEY_CURRENT_USER\\Software\\Microsoft\\VisualStudio\\10.0\\DialogPage\\Microsoft.DocWellBehavior.GeneralOptions \/v TabPanelPosition \/t REG_SZ \/d Bottom \/f<\/tt><\/p>\n<p>Tabs will then appear as shown in this image:<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2019\/05\/1738.tabpanelposition_bottom.png\" border=\"0\" \/><\/p>\n<p><a name=\"tabsonright\"><\/a><\/p>\n<h2>Tabs on right of document well<\/h2>\n<p>Run the following command to position tabs on the right of the document well:<\/p>\n<p><tt>reg add HKEY_CURRENT_USER\\Software\\Microsoft\\VisualStudio\\10.0\\DialogPage\\Microsoft.DocWellBehavior.GeneralOptions \/v TabPanelPosition \/t REG_SZ \/d Right \/f<\/tt><\/p>\n<p>Tabs will then appear as shown in this image:<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2019\/05\/4341.tabpanelposition_right.png\" border=\"0\" \/><\/p>\n<p><a name=\"coloroptions\"><\/a><\/p>\n<h2>Color Options<\/h2>\n<p><a name=\"customcolorforselected\"><\/a><\/p>\n<h2>Selected tab color options<\/h2>\n<p>Due to customer feedback, we have made the selected tab use a gradient when using custom colors, in order to make it more distinguishable:<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2019\/05\/3122.newselected.png\" border=\"0\" \/><\/p>\n<p>If you try one of the two options below and later wish to return to using a gradient, you can run the following command:<\/p>\n<p><tt>reg add\nHKEY_CURRENT_USER\\Software\\Microsoft\\VisualStudio\\10.0\\DialogPage\\Microsoft.DocWellBehavior.ColorGeneralOptions\n\/v SelectedOption \/t REG_SZ \/d FadeToVS \/f<\/tt><\/p>\n<h3><\/h3>\n<h3>Default custom color for selected tab<\/h3>\n<p>If you prefer to keep the color for the selected tab as was in the previous version, you can run the following command:<\/p>\n<p><tt>reg add\nHKEY_CURRENT_USER\\Software\\Microsoft\\VisualStudio\\10.0\\DialogPage\\Microsoft.DocWellBehavior.ColorGeneralOptions\n\/v SelectedOption \/t REG_SZ \/d Default \/f<\/tt><\/p>\n<p>You will then have the same behavior as before for the selected tab:<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2019\/05\/2110.darkcolortabs.png\" border=\"0\" \/><\/p>\n<p>&nbsp;<\/p>\n<h3>Use VS colors for selected tab<\/h3>\n<p>If you run the command below, the selected tab will use default VS colors always:<\/p>\n<p><tt>reg add HKEY_CURRENT_USER\\Software\\Microsoft\\VisualStudio\\10.0\\DialogPage\\Microsoft.DocWellBehavior.ColorGeneralOptions \/v SelectedOption \/t REG_SZ \/d VS \/f<\/tt><\/p>\n<p>This will also make it easier to distinguish it, as seen below:<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2019\/05\/2577.usecustomcolorforselected.png\" border=\"0\" \/><\/p>\n<p>&nbsp;<\/p>\n<p><a name=\"gradientsforcustom\"><\/a><\/p>\n<h2>Use gradients for custom colors<\/h2>\n<p>By default custom colors appear flat. You can run the following command to enable gradients for custom colors. This option might also help you to distinguish the active tab with custom colors enabled:<\/p>\n<p><tt>reg add HKEY_CURRENT_USER\\Software\\Microsoft\\VisualStudio\\10.0\\DialogPage\\Microsoft.DocWellBehavior.ColorGeneralOptions \/v ForceFlatColors \/t REG_SZ \/d False \/f<\/tt><\/p>\n<p>There are three different options for showing gradients for custom colors, described in the following paragraphs.<\/p>\n<p>&nbsp;<\/p>\n<p><a name=\"fadetodefault\"><\/a><\/p>\n<h3>Custom color fades to default tab color<\/h3>\n<p>Run the following command to make the tab gradient go from the custom color to the default Visual Studio tab color:<\/p>\n<p><tt>reg add HKEY_CURRENT_USER\\Software\\Microsoft\\VisualStudio\\10.0\\DialogPage\\Microsoft.DocWellBehavior.ColorGeneralOptions \/v FadeOption \/t REG_SZ \/d Default \/f<\/tt><\/p>\n<p>This will make colored tabs appear as shown in the following image:<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2019\/05\/6012.fadetodefault.png\" border=\"0\" \/><\/p>\n<p>Notice that gradient for unselected tabs starts with the custom color and fades to the default VS unselected tab color, which is transparent. The selected tab gradient starts with the custom color and fades to the default VS selected tab color, which is yellow.<\/p>\n<p>&nbsp;<\/p>\n<p><a name=\"fadetomoreintense\"><\/a><\/p>\n<h3>Custom color fades to more intense tab color<\/h3>\n<p>Run the following command to make the tab gradient go from the custom color to a more intense shade of the same custom color:<\/p>\n<p><tt>reg add HKEY_CURRENT_USER\\Software\\Microsoft\\VisualStudio\\10.0\\DialogPage\\Microsoft.DocWellBehavior.ColorGeneralOptions \/v FadeOption \/t REG_SZ \/d MoreIntense \/f<\/tt><\/p>\n<p>This option will make the tab gradient appear as follows:<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2019\/05\/3348.fadetomoreintense.png\" border=\"0\" \/><\/p>\n<p>&nbsp;<\/p>\n<p><a name=\"fadetolessintense\"><\/a><\/p>\n<h3>Custom color fades to less intense tab color<\/h3>\n<p>Run the following command to make the tab gradient go from the custom color to a less intense shade of the same custom color:<\/p>\n<p><tt>reg add HKEY_CURRENT_USER\\Software\\Microsoft\\VisualStudio\\10.0\\DialogPage\\Microsoft.DocWellBehavior.ColorGeneralOptions \/v FadeOption \/t REG_SZ \/d LessIntense \/f<\/tt><\/p>\n<p>This option will make the tab gradient appear as follows:<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2019\/05\/0042.fadetolessintense.png\" border=\"0\" \/><\/p>\n<p><a name=\"regexprecedence\"><\/a><\/p>\n<h2>Regular expression colors have precedence over project colors<\/h2>\n<p>By default, if you turn on both tab coloring by project and by regular expressions, regular expression colors will have precedence over project colors. You can run the following command to make project colors have precedence over regular expression colors instead:<\/p>\n<p><tt>reg add HKEY_CURRENT_USER\\Software\\Microsoft\\VisualStudio\\10.0\\DialogPage\\Microsoft.DocWellBehavior.ColorGeneralOptions \/v RegExHasPrecedence \/t REG_SZ \/d False \/f<\/tt><\/p>\n<p>&nbsp;<\/p>\n<h2><a name=\"regexoptions\"><\/a>Regular Expression Options<\/h2>\n<h2>Use full document path for regular expression match<\/h2>\n<p>By default, only the text that is visible in the tab is used to match regular expression for custom coloring. You can run the following command to instead match the full document path, which gives you greater flexibility:<\/p>\n<p><tt>reg add\nHKEY_CURRENT_USER\\Software\\Microsoft\\VisualStudio\\10.0\\DialogPage\\Microsoft.DocWellBehavior.GeneralOptions\n\/v UseFullPathForRegEx \/t REG_SZ \/d True \/f<\/tt><\/p>\n<p>&nbsp;<\/p>\n<h2><a name=\"changelog\"><\/a>Changelog<\/h2>\n<h2>Version 10.0.10710.22<\/h2>\n<ul>\n<li>Added to UI option to show\/hide pin button in unpinned tabs<\/li>\n<li>Removed UseCustomColorForSelected registry key, replaced with SelectedOption registry key<\/li>\n<li>Added registry key for matching full document path when using regular expressions for custom colors<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<h2>Tell Us What You Think<\/h2>\n<p>As always, we welcome your feedback. Please let us know if you find these options useful or not. You will find a hyperlink in our options dialog which you can use to provide us with feedback. You can also add comments to this post directly, add\/contribute to a discussion in the Visual Studio Gallery page for the Visual Studio 2010 Pro Power Tools, or send us feedback directly at docwell2010plus [at] microsoft.com.<\/p>\n<p>&nbsp;<\/p>\n<table border=\"0\" cellspacing=\"0\" cellpadding=\"2\">\n<tbody>\n<tr>\n<td valign=\"top\" width=\"112\"><img decoding=\"async\" src=\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2019\/05\/5353.radames.png\" border=\"0\" \/><\/td>\n<td valign=\"top\"><b>Radames Cruz Moreno<\/b> \u2013 Software Developer, Visual Studio Platform Team\n<b>Biography<\/b>: Radames arrived at Microsoft in 2008, just in time to help with development of Visual Studio 2010 since its early stages. He worked mainly helping develop the new WPF window docking system. Prior to that he worked in several interesting projects in Mexico using every technology and language imaginable, from C++ and Java to COBOL (<i>shudder<\/i>).<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"excerpt":{"rendered":"<p>[Update 7\/20\/2010]: Updated changes made for version 10.0.10710.22 of the Pro Power Tools. Please take a look at the changelog. A couple of posts ago I announced the availability of Document Well 2010 Plus as part of the Visual Studio 2010 Pro Power Tools. Since then we have received lots of feedback about our extension, [&hellip;]<\/p>\n","protected":false},"author":13,"featured_media":255385,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[155],"tags":[294,13],"class_list":["post-225284","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-visual-studio","tag-extensions","tag-visual-studio-2010"],"acf":[],"blog_post_summary":"<p>[Update 7\/20\/2010]: Updated changes made for version 10.0.10710.22 of the Pro Power Tools. Please take a look at the changelog. A couple of posts ago I announced the availability of Document Well 2010 Plus as part of the Visual Studio 2010 Pro Power Tools. Since then we have received lots of feedback about our extension, [&hellip;]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts\/225284","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/comments?post=225284"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts\/225284\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/media\/255385"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/media?parent=225284"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/categories?post=225284"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/tags?post=225284"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}