input

From RPTools Wiki
Revision as of 01:39, 10 February 2024 by Cold Ankles (talk | contribs) (Change note about image source update)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

input() Function

• Introduced in version 1.3b42
Allows the user to input several values at once via a modal dialog. The function takes one or more string arguments, one for each variable requiring assignment. Execution of the calling macro is paused while waiting for the user to interact with the input dialog.

Returns 1 if the user clicked the OK button, or 0 if they clicked Cancel (or hit Esc to exit the dialog). If input() returns 0, no variable assignments were made.

Note that there are no built-in mechanisms for input validation for TEXT input types.

Usage

input(inputField, ..., ...)

Parameters

  • inputField - A string containing various 'sub-parameters' that set the type and options of each inputField; requires at least one inputField but will accept a reasonably large amount. The inputFields can be set using a series of individual parameters, or as one or more String Lists. If a String List is used, the delimiter must be "##". This allows, among other things, for more dynamic input menus, with the number and type of input requests customized to the circumstances. Normally, each line is described by a string, wrapped in quotes, and the strings are separated by commas. The input function looks for unquoted commas to determine which strings are intended to be read as line entries. The function, however, can also recognize ## as a denotation of such a line break. Since this denotation can be surrounded by quotes more easily, it is possible to have a single string, wrapped in quotes, describe multiple input requests. The strings can be compiled in any number of ways: for instance using listAppend() and setting the delimiter to "##". Strings involving these ##'s can be intermixed with other standard strings. See the example below.

You declare the 'sub-parameters' of each inputField in the following manner:

  • "variableName|value|prompt|inputType|options"

Sub-Parameters

  • variableName - The name of the variable to which the value of the inputField is assigned.
  • value - The initial value present in the dialog box. If not present, it defaults to 0. In some cases you use a special syntax to indicate multiple values.
  • prompt - The prompt displayed to the user to indicate the meaning of the inputField.
  • inputType - Describes the type of input control presented to the user. Each of the different types are described in more detail below.
  • options - Contains one or more options that control the appearance of the input control or how information entered in the control is treated; options are given in the format option=value and separated by a space.

Input Types and Options

TEXT

Creates a text box containing the value or 0. The contents typed in the box are assigned to the variable, and there is no limit to the length of the data that can be entered.

TEXT Options
  • WIDTH=nnn - Sets the width of the text box; defaults to WIDTH=16.
  • SPAN=TRUE - Causes the prompt to be hidden and allows the inputField to span the width of the dialog; defaults to SPAN=FALSE. If hidden the prompt text is used as a tooltip.

LIST

Creates a drop-down list of choices. The variable is assigned the index (starting at 0) of the item that was selected. The value sub-parameter is a comma delimited list of the values that can be chosen.

LIST Options
  • SELECT=nnn - Sets the index of the initial selection in the drop-down list (the first item is number 0); defaults to SELECT=0.
  • VALUE=STRING - The variable is assigned the string contents of the selected item instead of the index; defaults to VALUE=NUMBER.
  • ICON=TRUE - If the string for the item contains a space and then an image asset URL, the image is displayed in the entry; defaults to ICON=FALSE. Text before the URL is used for the entry's text. The getTokenImage() and getStateImage() functions can be used to obtain asset URLs.
  • ICONSIZE=nnn - The size the icons; defaults to ICONSIZE=50. All icons are stretched to fit a square this size. If the asset URL points to an image that is not square, some distortion will occur.
  • TEXT=FALSE - No text is shown in the list entries next to the icons; defaults to TEXT=TRUE, and is ignored if no icon is set.
  • SPAN=TRUE - Causes the prompt to be hidden and allows the inputField to span the width of the dialog; defaults to SPAN=FALSE. If hidden the prompt text is used as a tooltip.
  • DELIMITER=, - The delimiter used in the list; defaults to the comma ,. The delimiter cannot contain empty spaces. If set to JSON, a JSON Array should be provided instead.

CHECK

Creates a checkbox. The variable is assigned either 0 (unchecked) or 1 (checked).

CHECK Options
  • SPAN=TRUE - Causes the prompt to be hidden and allows the inputField to span the width of the dialog; defaults to SPAN=FALSE. If hidden the prompt text is used as a tooltip.

RADIO

Creates a group of radio buttons. This option works much like LIST, returning the index of the choice that was selected.

RADIO Options
  • ORIENT=H - Arranges the radio buttons horizontally on a single line; defaults to ORIENT=V.
  • SELECT=nnn - Sets the initially selected radio button (the first item is number 0); defaults to SELECT=0.
  • VALUE=STRING - The variable is assigned the string contents of the selected item instead of the index; defaults to VALUE=NUMBER.
  • SPAN=TRUE - Causes the prompt to be hidden and allows the inputField to span the width of the dialog; defaults to SPAN=FALSE. If hidden the prompt text is used as title placed in the border of the radio button group.
  • DELIMITER=, - The delimiter used in the list; defaults to the comma ,. The delimiter cannot contain empty spaces. If set to JSON, a JSON Array should be provided instead.


LABEL

Creates a static label. The variableName is ignored, and nothing is assigned to it.

LABEL Options
  • ICON=TRUE - If the string for the value contains a space and then an image asset URL, the image is displayed; defaults to ICON=FALSE.
  • ICONSIZE=nnn - The size the icon; defaults to ICONSIZE=50. The icon is stretched to fit a square this size. If the asset URL points to an image that is not square, some distortion will occur.
  • TEXT=FALSE - The value is not shown; defaults to TEXT=TRUE.
  • SPAN=TRUE - Causes the prompt to be hidden and allows the inputField to span the width of the dialog; defaults to SPAN=FALSE. If hidden the prompt text is used as a tooltip.

PROPS

Creates a bordered sub-area containing multiple text boxes, one for each entry in a String Property List stored in value. The variableName is assigned a new string property containing all the entries with their updated values.

PROPS Options
  • SETVARS=SUFFIXED - Makes a variable assignment for each of the sub-values, with an underscore appended to the name; defaults to SETVARS=NONE.
  • SETVARS=UNSUFFIXED - Makes variable assignments to unmodified variable names. SUFFIXED is usually preferred, unless you are not using variable names that match Token Properties or if you specifically intend to overwrite them.
  • SPAN=TRUE - Causes the prompt to be hidden and allows the inputField to span the width of the dialog; defaults to SPAN=FALSE. If hidden the prompt text is used as title placed in the border of the PROPS group.
  • WIDTH=nnn - Sets the width of the input box; defaults to WIDTH=14.
  • TYPE=JSON - Result returned in variableName will be a JSON object instead of string property.

TAB

Creates a tab for a tabbed dialog box. The variableName variable gets assigned a String Property List containing all the variable assignments made on this tab. Since some of the variables may be property strings themselves, the tab property string uses the non-default delimiter "##". When using tabs, the first inputField must be a TAB.

TAB Options
  • SELECT=TRUE - Causes this tab to be displayed when the dialog appears; defaults to SELECT=FALSE.

TAB Example 

[H: input(
     "tab0 | Info || TAB", 
     "Name ## Rank ## Serial number | 1,2,3 || LIST",
     "tab1 | Abilities || TAB", 
     "Strength ## Dexterity ## Wisdom"
)]

Examples

1. A simple input() requesting 3 different text variables. 
[input("AtkBonus", "DmgBonus", "CombatAdvantage")]

Displays:

Note that only the variableName is required to generate an input dialog - if that is all that is provided, input() assumes that each variableName will be assigned using a text field.

2. A more complex input, including LABEL, CHECK, and TEXT fields. 

[h:status=input(
    "junkVar|"+powerClicked+"|Selected Power|LABEL",
    "ComAdv|0|Combat Advantage|CHECK",
    "MarkPenalty|0|Marked by an enemy other than your target|CHECK",
    "TargetConcealed|0|Target has Concealment|CHECK",
    "MiscBonus|0|Miscellaneous BONUSES to your attack roll",
    "MiscPenalty|0|Miscellaneous PENALTIES to your attack roll",
    "mdb|0|Miscellaneous BONUS to Damage")]
[h:abort(status)]

Displays:

Recall that junkVar, as the variableName for a LABEL control, has no value assigned to it. In this example, we assume powerClicked is a variable that is passed in some fashion to the macro generating this input. It is incorporated using the standard method of concatenating a variable into a string ("string text"+variable+"more string text"). Finally, observe that the variable status is assigned the value returned by the input() function, and the abort() function is called using the value of status. In this fashion, the macro is terminated if the user clicks the Cancel button or hits the ESC key.

3. An input showing several LIST boxes, as well as the VALUE=STRING option. 

[h:status=input(
    "targetNum|"+imgList+"|Select Target|LIST|SELECT=0 ICON=TRUE ICONSIZE=30",
    "feature|Hunter's Quarry, Sneak Attack, Warlock's Curse|Type of Striker Damage|LIST|SELECT=0 VALUE=STRING",
    "CQSDice|1d6,1d8,2d6,2d8,3d6,3d8|Curse, Quarry, or Sneak Attack Dice|LIST|SELECT=0 VALUE=STRING",
    "critAttack|0|Was the attack a critical hit?|CHECK"
)]

Displays:

Note that the prompt section for each list contains a list of items, or a variable containing a String List (e.g., the variable imgList). In the first list, the ICON and ICONSIZE options are set, because that list contains image asset URLs for token images. In the second two lists, the VALUE=STRING option is set so that the value in the corresponding variable is the actual string (e.g. "Sneak Attack") rather than the index of the list item.

Input using using the DELIMITER option for LIST. 

[h: colorjson = json.append("","Red","Blue","Green")]
[h: meatlist = "Duck;Goose;Chicken")]
[h: saucelist = "Mushroom GravyZZZOrange SauceZZZLemon Pepper"]
[h: res = input(
	"color|"+colorjson+"|Pick Color|LIST|VALUE=STRING DELIMITER=JSON",
	"meat|"+meatlist+"|Pick Dinner|LIST|VALUE=STRING DELIMITER=;",
    "sauce|"+saucelist+"|Pick Seasoning|LIST|VALUE=STRING DELIMITER=ZZZ"
)]
You chose: [r: color] [r: meat] with [r: sauce]

4. An input using the "##" delimiter technique. 

[h:inptext=""]
[h:num=1]

[h,foreach(entry,"SPD1,SPD2,SPD3,SPD4,SPD5,SPD6,SPD7,SPD8,SPD9"),code:{
  [if(num<=CMSL),code:{
    [inptext=listAppend(inptext,entry+"|"+eval(entry)+"|Level "+num,"##")]
  }]
  [num=num+1]
}]

[h:screen0=input(
  "junkvar|Include any bonus spells from high Wisdom|Enter your Cleric spells per day|LABEL",
  inptext
)]

In this example, variables SPD1-SPD9 and CMSL are called earlier from a token and represent spells per day for spell levels 1-9 and the maximum spell level accessible by the token at the moment for the class in question. The macro is intended to allow manual changing of the number of spells per day for the token, but the input is cleaned up and prevents complications by not allowing for inputs to spell levels beyond what is available. The first line in the input is a standard string, followed by a comma. The second is a "##"-containing string set by the [foreach():] function above, which will contain just the number of input requests, separated by ##'s, needed in the situation.

5. Dynamic Variable Example, by aliasmask. Uses strformat to create the property names and json.evaluate to put in default values.

If you are in need of an input() function where the number of inputs can vary like in ex. 4, you can also opt to use a json array and use json.evaluate(). This will look as follows: 

<!-- values needed either passed via function or hard coded in macro -->
[H: category = "Character"]
[H: prefix = "stat."]
[H: propList = json.append("","Strength","Dexterity","Constitution","Intelligence","Wisdom","Charisma")]
[H: defaults = json.append("","10","10","10","10","10","10")]

<!-- This is the dynamic part -->
   <!-- define the default values for the props -->
   [H: defaultVars = "{}"]
   [H, foreach(propName,propList): defaultVars = json.set(defaultVars,prefix + propName,json.get(defaults,roll.count))]

   <!-- get previously set values -->
   [H: vars = getProperty(category)]

   <!-- make sure all values are included by putting existing values over the default values -->
   [H, if(! json.isEmpty(vars)): vars = json.merge(defaultVars,vars); vars = defaultVars]

   <!-- define all vars locally -->
   [H: newPropList = json.toVars(vars)]

   <!-- Generate strings for input() -->
   [H: template = '%{prefix}%{propName}|[r: %{prefix}%{propName}]|%{propName}|TEXT']
   [H: inputStr = "[]"]
   [H, foreach(propName,propList): inputStr = json.append(inputStr,strformat(template))]

   <!-- get user Input -->
   [H: abort(input(json.toList(json.evaluate(inputStr),"##")))]

   <!-- save results. Note: we need json.fromVars() for better conversion -->
   [H: setProperty(category,json.fromStrProp(strPropFromVars(json.toList(newPropList),"UNSUFFIXED")))]
<!-- End of Dynamic Part -->

6. An input using aliasmask's no-zero-technique Usually, when you leave a value blank for input it puts that annoying 0 in it's place. Here's one way to avoid that. The only limitation, I suppose is that the variable name is visible as the prompt (and the variable name/contents must be StrProp-compatible).

(thanks to aliasmask for the technique and biodude for stating the limits.) 

[h:abort(input(
	"junk|<html><b>Enter player names. These should match the user names:<br><font color='red'>"+getAllPlayerNames()+"</font></html>|-|LABEL|SPAN=TRUE",
	"Enter Player Names|player0=;player1=;player2=||PROPS|SPAN=TRUE SETVARS=UNSUFFIXED"
))]

7. An input using Wolph42's tooltip-technique It is possible to use HTML mark up by just adding HTML tags around the input text. This makes it possible to use e.g. bold and italic tags, but also the span tag. This span tag allows tooltips to be added anywhere via its title attribute. Here's an example: 

[H: hasInput = input(
"junk|<html>Some title text</html>|<html>here comes the tooltip text</html>|LABEL|SPAN=TRUE",
"someVariable|0|<html><span title='<html>This text will be shown as a tooltip if you hover with your mouse over the text</html>'>Do you wish to turn the <b>setting</b> on?</span></html>|CHECK"
)]

Another interesting technique is adding pictures to the input. This example show the image of the selected token: 

[h:input(
	"junk|<html><b>Show picture of token<br></html>|-|LABEL|SPAN=TRUE",
	"junk|<html><img src='"+getTokenImage(60)+"'></img></html>|-|LABEL|SPAN=TRUE"
)]


b89 (b90 also?): input() no longer eats the colon ':'. And as the getTokenImage() will return 'asset://....' this will fail.

It might get fixed in b90 but if not, there is a workaround. Just change the last line into: 

"junk|<html><img src='"+
    replace(getTokenImage(), ":", "&#58;")+
    "' height=60 width=60></img></html>|-|LABEL|SPAN=TRUE"


As of version 1.7.0, a colon ":" may appear when an image is used in the prompt field if the image is not contained within a <body> element. The closing element is also required.


If you really want to go full monty on the tooltip INSIDE the input, here's an example of what is possible (the wiki can't properly handle all the code here so it comes out a bit funky): 

[h:hasInput 	= input('
	someVariable|0|<html><span title="<html>
	This setting allows for more advanced use of the movement limiter. First off: <b>In order for this to work <i>Limit Movement</i> must be<br>
	set to a number other then 0(the actual number wont be used).</b> If you enter 0 here then this setting will be ignored and the movement<br>
	will be limited to what you have set in <i>Limit Movement</i>.<br>
	<br>
	<b>Example of how to use this setting:</b><br>
	Let say that all the tokens have a characteristic: <i>Dexterity</i> and the max amount of cells a token is allowed to move is 4 x <i>Dexterity</i>.<br>
	Then what you set here is: <font bgcolor=white color=gray>[r:4*Dexterity]</font> You can enter any piece of code in here, as long as the output of that code<br>
	results in a number. The token that is moved will be the currentToken for this code! Note that if multiple tokens are moved, the first selected<br>
	token will be the currentToken.<br>
	<br>
	<b>Adding states and changing the output message</b>.<br>
	You can take this code even a step further and also change the output to the chat. This can be done by setting the predefined message variable to<br>
	something else. Here you can make use of other predefined variables as well. The default message is:<br>
	<font bgcolor=white color=gray>[h:message	= &quot;You moved %{tok} %{usedMove} cells. The maximum allowed movement is %{limitMovement} cells.&quot;]</font><br>
	(HTML make up can be used, but is removed from this example cause it does not show in a tool-tip) Here:<br>
	<font bgcolor=white color=gray>message</font> is the actual message to the ouput. Note that strformat is used.<br>
	<font bgcolor=white color=gray>tok</font> is the name of the selected token<br>
	<font bgcolor=white color=gray>usedMove</font> is the amount of cells the token moved<br>
	<font bgcolor=white color=gray>limitMovement</font> is the max amount the token is allowed to move.<br>
	These you can use to create your own message type <b>as long as the resulting output is a number</b>. E.g.:<br>
	<font bgcolor=white color=gray>
	[r,if(getState(&quot;Dead&quot;) &#124;&#124; getState(&quot;Incapacitated&quot;), CODE:{
		[r:0]	
		[h:message	= &quot;%{tok} is incapacitated and cannot move&quot;]
	};{
		[r:4*Dexterity]
	}]
	</font></html>">
	Enter code here (hover over this for more info)
	</html></span></html>
')]

For this to work I had to replace the quotes (") and the OR bars (||) by there ASCII representation. This is the result:

Note that this technique isn't perfect, because HTML tags inside the title may be interpreted as ending tags in the outer <html> block as the input() function is merely processing text and not looking at the content.

8. Images in Input It requires a bit of fiddling, but because HTML is allowed it's possible to add images to your input functions as well (besides the LIST technique described above). This can simply be done with the <html><img> tags. However the preset image size, e.g. from getTokenHandout(90) which retrieves the asset ID of the token handout and presets it to a max width or height (whichever is bigger) of 90 pixels, does work for LABEL but not for the rest! Example use: 

[h:input("junk|<html><img src='"+getTokenHandout(90)+"'></img></html>|-|LABEL|SPAN=TRUE")]
b89 (and possibly b90): this will not work anymore.

∗ 

As a workaround, use this: 

[h:input("junk|<html><img src='"+replace(getTokenHandout(), ":", "&#58;")+"' height=90 width=90></img></html>|-|LABEL|SPAN=TRUE")]

For other uses, e.g. choosing a picture from a RADIO option, you will need to limit the image sizes using the image tags: 

[h:me = getSelected()]
[h, token(me),CODE:{
	[image		= "<html><table><tr><td height='100'><img width=90 height=90 src='"+getTokenImage()+"'></img>	</td></tr><tr><td align='center'>Image</td>	</tr></table></html>"]
	[portrait	= "<html><table><tr><td height='100'><img width=90 height=90 src='"+getTokenPortrait()+"'></img>	</td></tr><tr><td align='center'>Portrait</td>	</tr></table></html>"]
	[handout	= "<html><table><tr><td height='100'><img width=90 height=90 src='"+getTokenHandout()+"'></img>	</td></tr><tr><td align='center'>Handout</td>	</tr></table></html>"]
}] 

[H: abort(input(
	"junk|<html><b>Choose picture to show to players:<br></html>|-|LABEL|SPAN=TRUE",
	"picChoice|"+image+","+portrait+","+handout+"|Which picture|RADIO|ORIENT=H SELECT=2",
	"picSize|100|Size of picture (px)"
))]

[r,token(me), if(picChoice == 0): "<img src='"+getTokenImage(picSize)+"'></img>"]
[r,token(me), if(picChoice == 1): "<img src='"+getTokenPortrait(picSize)+"'></img>"]
[r,token(me), if(picChoice == 2): "<img src='"+getTokenHandout(picSize)+"'></img>"]

9. Using PROPS 

[h: abort(input("resultVars|strength=0;toughness=0;willpower=0|Enter values|PROPS|SPAN=TRUE SETVARS=UNSUFFIXED"))]
[r:resultVars]

Version Changes

  • 1.6.0 - Added DELIMITER option to lists and radio lists.
  • 1.6.0 - Added WIDTH option to props type.
  • 1.6.0 - Added TYPE option to props type for JSON results.
  • 1.15.0 - image src URL can accept lib://path/to/image.jpg sources.
Retrieved from "https://wiki.rptools.info/index.php?title=input&oldid=17573"