Code/Tools/VisualStudioExtensions/CryEngineMonoDebugger/source/CryEngine.Debugger.Mono/CryEngineDebugPackage.vsct

   1 <?xml version="1.0" encoding="utf-8"?>
   2 <CommandTable xmlns="http://schemas.microsoft.com/VisualStudio/2005-10-18/CommandTable" xmlns:xs="http://www.w3.org/2001/XMLSchema">
   3
   4   <!--  This is the file that defines the actual layout and type of the commands.
   5         It is divided in different sections (e.g. command definition, command
   6         placement, ...), with each defining a specific set of properties.
   7         See the comment before each section for more details about how to
   8         use it. -->
   9
  10   <!--  The VSCT compiler (the tool that translates this file into the binary
  11         format that VisualStudio will consume) has the ability to run a preprocessor
  12         on the vsct file; this preprocessor is (usually) the C++ preprocessor, so
  13         it is possible to define includes and macros with the same syntax used
  14         in C++ files. Using this ability of the compiler here, we include some files
  15         defining some of the constants that we will use inside the file. -->
  16
  17   <!--This is the file that defines the IDs for all the commands exposed by VisualStudio. -->
  18   <Extern href="stdidcmd.h"/>
  19
  20   <!--This header contains the command ids for the menus provided by the shell. -->
  21   <Extern href="vsshlids.h"/>
  22
  23   <Extern href="VSDbgCmd.h"/>
  24   <Extern href="VsDebugGuids.h"/>
  25
  26   <!--The Commands section is where commands, menus, and menu groups are defined.
  27       This section uses a Guid to identify the package that provides the command defined inside it. -->
  28   <Commands package="guidCryEngineDebugPackage">
  29     <!-- Inside this section we have different sub-sections: one for the menus, another
  30     for the menu groups, one for the buttons (the actual commands), one for the combos
  31     and the last one for the bitmaps used. Each element is identified by a command id that
  32     is a unique pair of guid and numeric identifier; the guid part of the identifier is usually
  33     called "command set" and is used to group different command inside a logically related
  34     group; your package should define its own command set in order to avoid collisions
  35     with command ids defined by other packages. -->
  36
  37     <!-- In this section you can define new menu groups. A menu group is a container for
  38          other menus or buttons (commands); from a visual point of view you can see the
  39          group as the part of a menu contained between two lines. The parent of a group
  40          must be a menu. -->
  41     <Groups>
  42       <!-- Group for the Debug menu -->
  43       <Group guid="guidCryEngineDebugPackageCmdSet" id="CryEngineDebugTargetsGroup" priority="0x0300">
  44         <Parent guid="guidVSDebugGroup" id="IDM_DEBUG_MENU"/>
  45       </Group>
  46     </Groups>
  47
  48     <!--Buttons section. -->
  49     <!--This section defines the elements the user can interact with, like a menu command or a button
  50         or combo box in a toolbar. -->
  51     <Buttons>
  52       <!--To define a menu group you have to specify its ID, the parent menu and its display priority.
  53           The command is visible and enabled by default. If you need to change the visibility, status, etc, you can use
  54           the CommandFlag node.
  55           You can add more than one CommandFlag node e.g.:
  56               <CommandFlag>DefaultInvisible</CommandFlag>
  57               <CommandFlag>DynamicVisibility</CommandFlag>
  58           If you do not want an image next to your command, remove the Icon node /> -->
  59
  60       <!-- DEBUG MENU ITEM BUTTONS -->
  61       <Button guid="guidCryEngineDebugPackageCmdSet" id="GameLauncherCommandId" priority="0x0100" type="Button">
  62         <Parent guid="guidCryEngineDebugPackageCmdSet" id="CryEngineDebugTargetsGroup" />
  63         <Icon guid="guidImages" id="bmpPicStart" />
  64         <CommandFlag>DefaultInvisible</CommandFlag>
  65         <CommandFlag>DynamicVisibility</CommandFlag>
  66         <Strings>
  67           <ButtonText>Debug GameLauncher</ButtonText>
  68         </Strings>
  69       </Button>
  70
  71       <Button guid="guidCryEngineDebugPackageCmdSet" id="SandboxCommandId" priority="0x0100" type="Button">
  72         <Parent guid="guidCryEngineDebugPackageCmdSet" id="CryEngineDebugTargetsGroup" />
  73         <Icon guid="guidImages" id="bmpPicStart" />
  74         <CommandFlag>DefaultInvisible</CommandFlag>
  75         <CommandFlag>DynamicVisibility</CommandFlag>
  76         <Strings>
  77           <ButtonText>Debug Sandbox</ButtonText>
  78         </Strings>
  79       </Button>
  80
  81       <Button guid="guidCryEngineDebugPackageCmdSet" id="ServerCommandId" priority="0x0100" type="Button">
  82         <Parent guid="guidCryEngineDebugPackageCmdSet" id="CryEngineDebugTargetsGroup" />
  83         <Icon guid="guidImages" id="bmpPicStart" />
  84         <CommandFlag>DefaultInvisible</CommandFlag>
  85         <CommandFlag>DynamicVisibility</CommandFlag>
  86         <Strings>
  87           <ButtonText>Debug Server</ButtonText>
  88         </Strings>
  89       </Button>
  90       <!-- !DEBUG MENU ITEM BUTTONS -->
  91     </Buttons>
  92
  93     <!--The bitmaps section is used to define the bitmaps that are used for the commands.-->
  94     <Bitmaps>
  95       <!--  The bitmap id is defined in a way that is a little bit different from the others:
  96             the declaration starts with a guid for the bitmap strip, then there is the resource id of the
  97             bitmap strip containing the bitmaps and then there are the numeric ids of the elements used
  98             inside a button definition. An important aspect of this declaration is that the element id
  99             must be the actual index (1-based) of the bitmap inside the bitmap strip. -->
 100       <Bitmap guid="guidImages" href="Resources\LauncherCommands.png" usedList="bmpPicStart, bmpPic2, bmpPicSearch, bmpPicX, bmpPicArrows, bmpPicStrikethrough"/>
 101     </Bitmaps>
 102   </Commands>
 103
 104   <!-- Commands for the Debug Targets dropdown need to be added to this specific package. -->
 105   <Commands package="guidDebugTargetHandlerCmdSet">
 106     <Buttons>
 107       <!-- DEBUG TARGET DROPDOWN BUTTONS -->
 108       <Button guid="guidDebugTargetHandlerCmdSet" id="GameLauncherCommandId" priority="0x1000" type="Button">
 109         <Parent guid="guidDebugTargetHandlerCmdSet" id="DebugTargetMenuControllerGroup"/>
 110         <Icon guid="guidImages" id="bmpPicStart" />
 111         <CommandFlag>DefaultInvisible</CommandFlag>
 112         <CommandFlag>DynamicVisibility</CommandFlag>
 113         <Strings>
 114           <ButtonText>Debug GameLauncher</ButtonText>
 115         </Strings>
 116       </Button>
 117
 118       <Button guid="guidDebugTargetHandlerCmdSet" id="SandboxCommandId" priority="0x1000" type="Button">
 119         <Parent guid="guidDebugTargetHandlerCmdSet" id="DebugTargetMenuControllerGroup"/>
 120         <Icon guid="guidImages" id="bmpPicStart" />
 121         <CommandFlag>DefaultInvisible</CommandFlag>
 122         <CommandFlag>DynamicVisibility</CommandFlag>
 123         <Strings>
 124           <ButtonText>Debug Sandbox</ButtonText>
 125         </Strings>
 126       </Button>
 127
 128       <Button guid="guidDebugTargetHandlerCmdSet" id="ServerCommandId" priority="0x1000" type="Button">
 129         <Parent guid="guidDebugTargetHandlerCmdSet" id="DebugTargetMenuControllerGroup"/>
 130         <Icon guid="guidImages" id="bmpPicStart" />
 131         <CommandFlag>DefaultInvisible</CommandFlag>
 132         <CommandFlag>DynamicVisibility</CommandFlag>
 133         <Strings>
 134           <ButtonText>Debug Server</ButtonText>
 135         </Strings>
 136       </Button>
 137       <!-- /DEBUG BUTTONS -->
 138     </Buttons>
 139   </Commands>
 140
 141   <Symbols>
 142     <!-- This is the package guid. -->
 143     <GuidSymbol name="guidCryEngineDebugPackage" value="{5e1711f6-3c97-41b2-96f0-4f05be71eb19}" />
 144
 145     <!-- This is the guid used to group the menu commands together -->
 146     <GuidSymbol name="guidCryEngineDebugPackageCmdSet" value="{5f0ed1f6-570c-4a93-a2d0-bf15e7054a90}">
 147       <IDSymbol name="CryEngineDebugTargetsGroup" value="0x1020" />
 148       <IDSymbol name="GameLauncherCommandId" value="0x02001" />
 149       <IDSymbol name="SandboxCommandId" value="0x02002" />
 150       <IDSymbol name="ServerCommandId" value="0x02003" />
 151     </GuidSymbol>
 152
 153     <GuidSymbol name="guidDebugTargetHandlerCmdSet" value="{6E87CFAD-6C05-4adf-9CD7-3B7943875B7C}">
 154       <IDSymbol name="DebugTargetMenuControllerGroup" value="0x1000" />
 155       <IDSymbol name="DebugTargetMenuControllerFooterGroup" value="0x2000" />
 156       <IDSymbol name="DebugTargetMenuController" value="0x0100" />
 157       <IDSymbol name="cmdidDebugTargetAnchorItem" value="0x0101" />
 158       <IDSymbol name="GameLauncherCommandId" value="0x02001" />
 159       <IDSymbol name="SandboxCommandId" value="0x02002" />
 160       <IDSymbol name="ServerCommandId" value="0x02003" />
 161     </GuidSymbol>
 162
 163     <GuidSymbol name="guidImages" value="{94f36f14-d8dd-4801-8b8d-d8473a417947}" >
 164       <IDSymbol name="bmpPicStart" value="1" />
 165       <IDSymbol name="bmpPic2" value="2" />
 166       <IDSymbol name="bmpPicSearch" value="3" />
 167       <IDSymbol name="bmpPicX" value="4" />
 168       <IDSymbol name="bmpPicArrows" value="5" />
 169       <IDSymbol name="bmpPicStrikethrough" value="6" />
 170     </GuidSymbol>
 171   </Symbols>
 172 </CommandTable>