This documentation is archived and is not being maintained.


Determines the visual style of the marker.

Namespace: Microsoft.VisualStudio.TextManager.Interop
Assembly: Microsoft.VisualStudio.TextManager.Interop (in microsoft.visualstudio.textmanager.interop.dll)

public enum MARKERVISUAL
public enum MARKERVISUAL
public enum MARKERVISUAL

 Member nameDescription
MV_BORDERIndicates that a box is drawn around the marked text. The border is not necessarily a square in the case of a multi-line marker. You can specify either a solid or dashed line. For more information, refer to the GetDefaultLineStyle method. 
MV_COLOR_ALWAYSIndicates that the marked text should always be colored inline. This option is exclusive of the MV_COLOR_LINE_IF_NO_MARGIN option. 
MV_COLOR_LINE_IF_NO_MARGINIndicates that the marked text should be colored only if the widget margin is hidden. This option is exclusive of the MV_COLOR_ALWAYS option. 
MV_COLOR_SPAN_IF_ZERO_LENGTHIndicates that a marker should paint as a solid bar if the text span is of zero length. This setting should not be used for markers such as wavy lines, because the line will appear only as a solid bar. 
MV_CONTEXT_CONTRIBUTION_FOR_BODYIndicates that the body of a marker wants to contribute context, and thus its client can be queried for IVsUserContextUpdate
MV_DRAGGABLE_GLYPHIndicates that a glyph can take part in drag and drop operations. In addition to MV_DRAGGABLE_GLYPH, a marker that allows dragging should also specify MV_GLYPH_HOVER_CURSOR, so that the editor knows to provide a custom cursor for the mouse when it passes over the glyph. These visual styles can either be set for the marker type (if all markers of the given type have the same behavior) or for a given marker instance. The text view negotiates the hover cursor and drag initiation by calling QueryInterface on the marker client provided (IVsTextMarkerClient). The client object should implement IVsMouseCursorProvider to handle mouse cursor updates for MV_GLYPH_HOVER_CURSOR and IVsTextMarkerGlyphDropHandler to handle drop negotiation. 
MV_FORCE_INVISIBLEForces the marker to be invisible. Use this setting to toggle a marker between being visible and invisible, which is faster than using SetType
MV_GLYPHCan show a glyph in the widget margin. This indicates that you want to draw a margin glyph. Draw the glyph using DrawGlyphWithColors. If the widget margin does not exist, depending on the window and on the user's preferences, then the glyph is not visible. 
MV_GLYPH_HOVER_CURSORIndicates that the client has requested a callback (via their client interface) to set the mouse cursor when the user hovers the mouse over the glyph. 
MV_LINEMarker is only a line adornment and does not otherwise affect coloring. Thus, the marker is some form of underline style. Currently, the only supported form of this is a wavy line. 
MV_MULTILINE_GLYPHIndicates that a glyph spans multiple lines. This enables the drawing of multi-line glyphs. If you specify this flag, your IDrawGlyphWithColors handler is called with the GDF_MULTILINE flag, and often with GDF_BOTTOMEDGE, depending on the scenario. 
MV_SEL_MARGIN_GLYPHSimilar to MV_GLYPH, but indicates that the glyph lives in the selection margin, not the normal widget margin. 
MV_TIP_FOR_BODYDetermines whether a tip should be shown for the body of the marker text. The MV_TIP_FOR_BODY and MV_TIP_FOR_GLYPH options are dependant on one another. If this value is set, marked text will trigger a tool tip over the body or glyph. However, as the marker type provider, you are not allowed to specify what text shows up. This is handled by the GetTipTexthandler of whoever created the given marker instance. 
MV_TIP_FOR_GLYPHDetermines whether a tip should be shown in the widget margin. 

COM Signature

From textmgr.idl: