The Caption for the Code Window seems to be read only for any window that is
NOT a toolwindow. Is there any way to PAINT or otherwise set the caption
for a code window?
A few employees here don't like the fact that we have the same name for our
Common.vb module in different projects under the same solution. When they
have 3 of the same named modules open, they have a hard time distinguishing
them. So I'm trying to help by "painting" the type of project the module is
under "DAL, BLL, Schema, WebUI, UI, et cetera" where the filename is in the
tab.
Any help would be appreciated.
Mythran
"Ed Dore [MSFT]" - 02 Dec 2004 23:18 GMT
Hi Mythran,
There isn't any way to do this from an add-in scenario. The Code Window's
caption is controlled by the code editor itself, but I suspect you can
change it by calling IVsWindowFrame::SetProperty.
I had a customer that implementedh a custom editor, and was attempting to
set the caption via IVsWindowFrame::SetProperty(VSFPROPID_Caption,
someBSTR) call, but it didn't work. A bit of digging and a little advice
from one of the VSIP developers we found that you need to set the caption
for document windows using the VSFPROPID_OwnerCaption and
VSFPROPID_EditorCaption properties.
Sincerely,
Ed Dore [MSFT]
This post is 'AS IS' with no warranties, and confers no rights.
Mythran - 03 Dec 2004 16:35 GMT
> Hi Mythran,
>
[quoted text clipped - 13 lines]
>
> This post is 'AS IS' with no warranties, and confers no rights.
Now, how would I go about doing this in VB.Net?
Thanks fer ya reply btw.
:)
Mythran
Ed Dore [MSFT] - 08 Dec 2004 03:35 GMT
Hi Mythran,
You need to download and install the VSIP SDK and the VSIP Extras SDK. This
will allow you to create VSIP packages with VB .Net. Next you'll need to
create a VSIP package project, and implement your custom editor. There
aren't really any samples for VB .Net that come with the VSIP Extras SDK.
It's all C++ and C#. There is one simply toolwindow package implemented in
VB .Net that you could possibly use as a starting point, and then review the
C# BasicEditor sample for ideas on how to implement an editor.
Sincerely,
Ed Dore [MSFT]
This post is 'AS IS' with no warranties, and confers no rights.
Mythran - 08 Dec 2004 16:48 GMT
> Hi Mythran,
>
[quoted text clipped - 10 lines]
>
> This post is 'AS IS' with no warranties, and confers no rights.
I understand the VSIP packages ... started writing a package for a custom
language set quite awhile ago. :) Got Bison installed but never finished
the project...oh well, maybe next time :)
Anywho, thanks for your input :)
Mythran