1dot13/source
1
0
Fork 0
mirror of https://github.com/1dot13/source.git synced 2026-08-12 14:10:23 +02:00
Code Issues Packages Projects Releases Wiki Activity

Merged New Inventory Project into main branch

Browse Source 
git-svn-id: https://ja2svn.mooo.com/source/ja2/trunk/GameSource/ja2_v1.13/Build@1871 3b4a5df2-a311-0410-b5c6-a8a6f20db521
This commit is contained in:
lalien
2008-03-08 15:15:25 +00:00
parent e16d166277
commit 43ca24dda8
649 changed files with 93359 additions and 82507 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Utils/Text Input.h
+45 -45
View File
@@ -3,33 +3,33 @@
#include "input.h"
//AUTHOR: Kris Morness
//AUTHOR: Kris Morness
//Intended for inclusion with SGP.
//NEW CHANGES: January 16, 1998
//I have added the ability to stack the text input modes. So, if you have a particular
//NEW CHANGES: January 16, 1998
//I have added the ability to stack the text input modes. So, if you have a particular
//screen that has fields, then somehow, hit a key to go into another mode with text input,
//it will automatically disable the current fields, as you go on to define new ones. Previously,
//you would have to make sure the mode was removed before initializing a new one. There were
//it will automatically disable the current fields, as you go on to define new ones. Previously,
//you would have to make sure the mode was removed before initializing a new one. There were
//potential side effects of crashes, and unpredictable results, as the new fields would cook the
//existing ones.
//NOTE: You may have to modify you code now, so that you don't accidentally kill a text input mode
//when you don't one to begin with. (like removing an already deleted button). Also, remember that
//NOTE: You may have to modify you code now, so that you don't accidentally kill a text input mode
//when you don't one to begin with. (like removing an already deleted button). Also, remember that
//this works like a stack system and you can't flip through existing defined text input modes at will.
//NOTES ON LIMITATIONS:
// -max number of fields 255 (per level)
// -max num of chars in field 255
// -max num of chars in field 255
//These are the definitions for the input types. I didn't like the input filter idea,
//and the lack of freedom it gives you. This method is much simpler to use.
//NOTE: Uppercase/lowercase filters ensures that all input is either all uppercase or lowercase
//NOTE: Feel free to expand this to your needs, though you also need to support it in the filter
// section.
//These are the definitions for the input types. I didn't like the input filter idea,
//and the lack of freedom it gives you. This method is much simpler to use.
//NOTE: Uppercase/lowercase filters ensures that all input is either all uppercase or lowercase
//NOTE: Feel free to expand this to your needs, though you also need to support it in the filter
// section.
#define INPUTTYPE_NUMERICSTRICT 0x0001 //0-9 only, no minus signs.
#define INPUTTYPE_ALPHA 0x0002 //a-z A-Z
#define INPUTTYPE_SPACES 0x0004 //allows spaces in input
#define INPUTTYPE_SPECIAL 0x0008 // !@#$%^&*()_+`|\[]{};':"<>,./? (spaces not included)
#define INPUTTYPE_SPECIAL 0x0008 // !@#$%^&*()_+`|\[]{};':"<>,./? (spaces not included)
#define INPUTTYPE_UPPERCASE 0x0010 //converts all lowercase to uppercase
#define INPUTTYPE_LOWERCASE 0x0020 //converts all uppercase to lowercase
#define INPUTTYPE_FIRSTPOSMINUS 0x0002 //allows '-' at beginning of field only
@@ -39,12 +39,12 @@
#define INPUTTYPE_ASCII (INPUTTYPE_ALPHANUMERIC | INPUTTYPE_SPECIALCHARS)
//DON'T GO ABOVE INPUTTYPE_EXCLUSIVE_BASEVALUE FOR INPUTTYPE MASKED VALUES LISTED ABOVE!!!
#define INPUTTYPE_EXCLUSIVE_BASEVALUE 0x1000 //increase this value if necessary
#define INPUTTYPE_EXCLUSIVE_BASEVALUE 0x1000 //increase this value if necessary
//Exclusive handlers
//The dosfilename inputtype is a perfect example of what is a exclusive handler.
//In this method, the input accepts only alphas and an underscore as the first character,
//then alphanumerics afterwards. For further support, chances are you'll want to treat it
//then alphanumerics afterwards. For further support, chances are you'll want to treat it
//as an exclusive handler, and you'll have to process it in the filter input function.
enum
{
@@ -54,15 +54,15 @@ enum
//INPUTTYPE_EXCLUSIVE_NEWNEWNEW, etc...
};
//Simply initiates that you wish to begin inputting text. This should only apply to screen
//initializations that contain fields that edit text. It also verifies and clears any existing
//fields. Your input loop must contain the function HandleTextInput and processed if the gfTextInputMode
//flag is set else process your regular input handler. Note that this doesn't mean you are necessarily typing,
//just that there are text fields in your screen and may be inactive. The TAB key cycles through your text fields,
//Simply initiates that you wish to begin inputting text. This should only apply to screen
//initializations that contain fields that edit text. It also verifies and clears any existing
//fields. Your input loop must contain the function HandleTextInput and processed if the gfTextInputMode
//flag is set else process your regular input handler. Note that this doesn't mean you are necessarily typing,
//just that there are text fields in your screen and may be inactive. The TAB key cycles through your text fields,
//and special fields can be defined which will call a void functionName( UINT16 usFieldNum )
void InitTextInputMode();
//A hybrid version of InitTextInput() which uses a specific scheme. JA2's editor uses scheme 1, so
//A hybrid version of InitTextInput() which uses a specific scheme. JA2's editor uses scheme 1, so
//feel free to add new color/font schemes.
enum{
DEFAULT_SCHEME
@@ -71,14 +71,14 @@ void InitTextInputModeWithScheme( UINT8 ubSchemeID );
//Clears any existing fields, and ends text input mode.
void KillTextInputMode();
//Kills all levels of text input modes. When you init a second consecutive text input mode, without
//first removing them, the existing mode will be preserved. This function removes all of them in one
//Kills all levels of text input modes. When you init a second consecutive text input mode, without
//first removing them, the existing mode will be preserved. This function removes all of them in one
//call, though doing so "may" reflect poor coding style, though I haven't thought about any really
//just uses for it :(
void KillAllTextInputModes();
//Saves the current text input mode, then removes it and activates the previous text input mode,
//if applicable. The second function restores the settings. Doesn't currently support nested
//if applicable. The second function restores the settings. Doesn't currently support nested
//calls.
void SaveAndRemoveCurrentTextInputMode();
void RestoreSavedTextInputMode();
@@ -86,31 +86,31 @@ void RestoreSavedTextInputMode();
void SetTextInputCursor( UINT16 usNewCursor );
UINT16 GetTextInputCursor();
//After calling InitTextInputMode, you want to define one or more text input fields. The order
//of calls to this function dictate the TAB order from traversing from one field to the next. This
//After calling InitTextInputMode, you want to define one or more text input fields. The order
//of calls to this function dictate the TAB order from traversing from one field to the next. This
//function adds mouse regions and processes them for you, as well as deleting them when you are done.
void AddTextInputField( INT16 sLeft, INT16 sTop, INT16 sWidth, INT16 sHeight, INT8 bPriority,
STR16 szInitText, UINT8 ubMaxChars, UINT16 usInputType );
STR16 szInitText, UINT8 ubMaxChars, UINT16 usInputType );
//This allows you to insert special processing functions and modes that can't be determined here. An example
//would be a file dialog where there would be a file list. This file list would be accessed using the Win95
//convention by pressing TAB. In there, your key presses would be handled differently and by adding a userinput
//field, you can make this hook into your function to accomplish this. In a filedialog, alpha characters
//This allows you to insert special processing functions and modes that can't be determined here. An example
//would be a file dialog where there would be a file list. This file list would be accessed using the Win95
//convention by pressing TAB. In there, your key presses would be handled differently and by adding a userinput
//field, you can make this hook into your function to accomplish this. In a filedialog, alpha characters
//would be used to jump to the file starting with that letter, and setting the field in the text input
//field. Pressing TAB again would place you back in the text input field. All of that stuff would be handled
//field. Pressing TAB again would place you back in the text input field. All of that stuff would be handled
//externally, except for the TAB keys.
typedef void (*INPUT_CALLBACK)(UINT8,BOOLEAN);
void AddUserInputField( INPUT_CALLBACK userFunction );
//INPUT_CALLBACK explanation:
//The function must use this signature: void FunctionName( UINT8 ubFieldID, BOOLEAN fEntering );
//The function must use this signature: void FunctionName( UINT8 ubFieldID, BOOLEAN fEntering );
//ubFieldID contains the fieldID of that field
//fEntering is true if you are entering the user field, false if exiting.
//Removes the specified field from the existing fields. If it doesn't exist, then there will be an
//Removes the specified field from the existing fields. If it doesn't exist, then there will be an
//assertion failure.
void RemoveTextInputField( UINT8 ubField );
//This is a useful call made from an external user input field. Using the previous file dialog example, this
//This is a useful call made from an external user input field. Using the previous file dialog example, this
//call would be made when the user selected a different filename in the list via clicking or scrolling with
//the arrows, or even using alpha chars to jump to the appropriate filename.
void SetInputFieldStringWith16BitString( UINT8 ubField, const STR16 szNewText );
@@ -126,10 +126,10 @@ UINT16 GetExclusive24HourTimeValueFromField( UINT8 ubField );
void SetExclusive24HourTimeValue( UINT8 ubField, UINT16 usTime );
//Converts the field's string into a number, then returns that number
//returns -1 if blank or invalid. Only works for positive numbers.
//returns -1 if blank or invalid. Only works for positive numbers.
INT32 GetNumericStrictValueFromField( UINT8 ubField );
//Converts a number to a numeric strict value. If the number is negative, the
//Converts a number to a numeric strict value. If the number is negative, the
//field will be blank.
void SetInputFieldStringWithNumericStrictValue( UINT8 ubField, INT32 iNumber );
@@ -138,12 +138,12 @@ void SetActiveField( UINT8 ubField );
void SelectNextField();
void SelectPrevField();
//Returns the active field ID number. It'll return -1 if no field is active.
//Returns the active field ID number. It'll return -1 if no field is active.
INT16 GetActiveFieldID();
//These allow you to customize the general color scheme of your text input boxes. I am assuming that
//under no circumstances would a user want a different color for each field. It follows the Win95 convention
//that all text input boxes are exactly the same color scheme. However, these colors can be set at anytime,
//These allow you to customize the general color scheme of your text input boxes. I am assuming that
//under no circumstances would a user want a different color for each field. It follows the Win95 convention
//that all text input boxes are exactly the same color scheme. However, these colors can be set at anytime,
//but will effect all of the colors.
void SetTextInputFont( UINT16 usFont );
void Set16BPPTextFieldColor( UINT16 usTextFieldColor );
@@ -155,13 +155,13 @@ void SetBevelColors( UINT16 usBrighterColor, UINT16 usDarkerColor );
void SetCursorColor( UINT16 usCursorColor );
//All CTRL and ALT keys combinations, F1-F12 keys, ENTER and ESC are ignored allowing
//processing to be done with your own input handler. Otherwise, the keyboard event
//processing to be done with your own input handler. Otherwise, the keyboard event
//is absorbed by this input handler, if used in the appropriate manner.
//This call must be added at the beginning of your input handler in this format:
//while( DequeueEvent(&Event) )
//{
// if( !HandleTextInput( &Event ) && (your conditions...ex: Event.usEvent == KEY_DOWN ) )
// {
// if( !HandleTextInput( &Event ) && (your conditions...ex: Event.usEvent == KEY_DOWN ) )
// {
// switch( Event.usParam )
// {
// //Normal key cases here.