/// <summary>Basic keyboard/input functionality required by the CommandConsole(Base) class</summary>
publicinterfaceIConsoleKeyboard
{
/// <summary>The current state of the keyboard as of the last Update</summary>
KeyboardStateCurrentKeyboardState
{
get;
}
/// <summary>Collection of keys that are newly pressed (i.e. not held) as of the last Update</summary>
IList<Keys>NewlyPressedKeys
{
get;
}
/// <summary>Collection of keys that are being held fown (i.e. not newly pressed) as of the last Update</summary>
IList<Keys>HeldKeys
{
get;
}
}
#endregion
#regionCVarObject
// JRT: OK - Why Is This In Its Own File? Because Of The Way The Type System Works In .NET. If You Create
// JRT: Two Completely Identical Types, But Put Them In Different Assemblies, They Are Considered To Be
// JRT: Two Completely DIFFERENT Types, Even Though They Are Compatible With One Another. By Putting
// JRT: The CVar Class Into A Separate Assembly, Both The CommandConsole And External Functions
// JRT: Reference The Same Type, Allowing Us To Pass CVars Back And Forth.
/// <summary>Object that wraps the functionality of a console variable -- defined separately because external functions will receive CVar instances</summary>
publicclassCVar
{
/// <summary>The storage for the Name property</summary>
protectedstringm_name=String.Empty;
/// <summary>The storage for the Value property</summary>
protectedobjectm_value=null;
/// <summary>The string name for this console variable</summary>