# $ K + What is a minidriver workspace?
A minidriver workspace is a file unique to the Minidriver Development Tool.  It does the following for you:
·	Tracks many of the files used to create a minidriver resource DLL, and their resource Ids.  This includes the RC file, and any GTT or UFM files used in the project.
·	Tracks the GPD files which use the resource DLL.  The workspace is thus resource DLL-centric, rather than GPD file-centric.
·	Organizes and maintains consistency information when a minidriver is converted.
·	Maintains error logs for all of the GPD files associated with the workspace.  These logs are maintained within the workspace file- they are not left on your disk.
The workspace will work best when all of the GPD files associated with a resource DLL are contained in the workspace.  This is because the workspace will contain the necessary information to resolve identifiers for fonts and other resources.  GPD files can be imported into a workspace, and deleted from it.

# $ K + The Workspace Editor Window
The workspace editor is based on a single tree view control:
{bml WORKED00.SHG}
The root level is named the same as your RC file, but you may change this and most other labels to suit your tastes.  Beneath it are three children: the device font files, the translation tables (a.k.a. glyph maps), and the model information, which is the collection of GPD files associated with the workspace.  The number of items the node contains is a part of each node’s label.  These labels cannot be edited.
Each node beneath this level represents a UFM, GTT, or GPD file.  Again, each node has a label- the GPD label is the original model name, if converted- otherwise, it is the base file name.  The others use the original file name.  These labels may also be edited.  Beneath each of these is a file name node.  This can be edited to rename the underlying file- in the case of a GPD file, the path may also be edited, which will result in the file being moved to a different location.
The keyboard interface here is fairly standard, and resembles the Windows Explorer.  Some common keys:
F2- edits the label, if it can be edited.
F10- brings up an editing menu appropriate to the current node.
Up, down, Page up, Page down cursor keys- these navigate the tree without expanding or contracting it.
Left and right cursor keys- these will expand (right) and collapse (left) the tree at the current node.
Delete- will remove the current item.  In the Beta 1 version, only GPD files may be removed from a workspace.
Enter- will take an appropriate default action.  For most nodes, this is to expand or collapse the node.  On the label for a file, it will cause the file to be edited.
The mouse usage is also fairly standard.  Double clicking a file label will cause the file to be edited.  You may also edit labels by holding down the left mouse button after selecting the item.  A right click will bring up an appropriate context menu.

# $ Workspace file name
The title bar will contain the workspace file name (or Untitled, where a new, unsaved workspace is being edited).  Title bars for resource or GPD file editors launched from the workspace editor will have a title bar with the workspace name and the resource name, separated by a colon.  This can make it easier to identify what resources are being edited if multiple workspaces are being used.

# $ Resource DLL label
This entry is the resource script file (RC file) base name.  It can be altered if you want to do so.  Renaming this label has no effect on the RC file name or anything else in the workspace in the current version of the program.

# $ Device font list
This node identifies the number of device fonts contained in the resource DLL.  Each font is a separate UFM file.  This node can be expanded to show the entire font list by clicking the button next to the label, selecting the Expand item from the context menu, or using the right arrow key when the label has the focus.

# $ Translation Table List
This node identifies the number of translation tables contained in the resource DLL.  Each table is a separate GTT file. This node can be expanded to show the entire font list by clicking the button next to the label, selecting the Expand item from the context menu, or using the right arrow key when the label has the focus.

# $ Printer Model List
This identifies the number of printer models associated with the resource DLL.  Each model will represent a separate GPD file. This node can be expanded to show the entire font list by clicking the button next to the label, selecting the Expand item from the context menu, or using the right arrow key when the label has the focus.

# $ K + Renaming files with the workspace editor
Each file in the workspace (except for the RC file) can be renamed using the workspace editor.
1.	Locate the node in the tree that corresponds to the item whose file you wish to rename.
2.	Click the button to expose the File Name: node.
3.	Press F2 or use the editing menu for the node to rename the node.
4.	Type in the new file name, and press Enter.
If the file cannot be renamed, a message box will inform you of this.  Otherwise, the file will be renamed.
Moving GPD files
If you perform the above procedure on a GPD file node, the full path name is available for editing.  You can move the file, as well as renaming it, by editing the path information in the file name.

# $ K + Launching a resource or GPD file editor
To do this, do any of the following:
·	Double click on the item you wish to edit.
·	Press the enter key when the focus is on the item.
·	Select Open from the editing menu for the item.

# $ K + Removing a GPD file from the workspace
To remove a GPD file from the workspace, do any of the following:
·	Select the model, and press the Delete key.
·	Right click the item, and select the Delete menu item.
You will be presented with a GPD deletion verification dialog.

# $ K + GPD Deletion Query
This is displayed when you ask to remove a GPD file from the workspace.
{bmc gpdzap.BMP} 
Check the check box if you wish to delete the file itself.  Otherwise, only the record of the file in the workspace is expunged.