Difference between revisions of "Sheet Worker Snippets"
From Roll20 Wiki
Andreas J. (Talk | contribs) m |
Andreas J. (Talk | contribs) m (formatting) |
||
Line 5: | Line 5: | ||
Your best bet would be to avoid the autocalc fields entirely if you can. Monitor the two other fields and when they change, have a sheetworker that adds them up to the new value. Then you can refer to the new value in other calculations much easier. | Your best bet would be to avoid the autocalc fields entirely if you can. Monitor the two other fields and when they change, have a sheetworker that adds them up to the new value. Then you can refer to the new value in other calculations much easier. | ||
− | <pre> | + | <pre data-language="javascript"> |
on("sheet:opened change:stat_a change:stat_b", function() { | on("sheet:opened change:stat_a change:stat_b", function() { | ||
getAttrs(["stat_a", "stat_b"], function(values) { | getAttrs(["stat_a", "stat_b"], function(values) { | ||
Line 22: | Line 22: | ||
I generally don't put my working in the setattrs call, but before it so i can more easily check it. Something like | I generally don't put my working in the setattrs call, but before it so i can more easily check it. Something like | ||
− | <pre> | + | <pre data-language="javascript"> |
on("sheet:opened change:stat_a change:stat_b", function() { | on("sheet:opened change:stat_a change:stat_b", function() { | ||
getAttrs(["stat_a", "stat_b"], function(values) { | getAttrs(["stat_a", "stat_b"], function(values) { | ||
Line 40: | Line 40: | ||
(credit: [https://app.roll20.net/users/157788 GiGs]) | (credit: [https://app.roll20.net/users/157788 GiGs]) | ||
Many sheet workers have a bunch of lines like this: | Many sheet workers have a bunch of lines like this: | ||
− | <pre> | + | <pre data-language="javascript"> |
var stat_a = parseInt(values["stat_a"],10)||0; | var stat_a = parseInt(values["stat_a"],10)||0; | ||
var stat_b = parseInt(values["stat_b"],10)||0; | var stat_b = parseInt(values["stat_b"],10)||0; | ||
</pre> | </pre> | ||
You might also have lines like this: | You might also have lines like this: | ||
− | <pre> | + | <pre data-language="javascript"> |
setAttrs({ | setAttrs({ | ||
"foo_modchars": parseInt(values["stat_a"],10) || 0 + parseInt(values["stat_b"],10) || 0 | "foo_modchars": parseInt(values["stat_a"],10) || 0 + parseInt(values["stat_b"],10) || 0 | ||
Line 51: | Line 51: | ||
</pre> | </pre> | ||
It gets tedious typing out all that. With the function below, you would instead write them as: | It gets tedious typing out all that. With the function below, you would instead write them as: | ||
− | <pre> | + | <pre data-language="javascript"> |
var stat_a = parseValues("stat_a"); | var stat_a = parseValues("stat_a"); | ||
var stat_b = parseValues("stat_b"); | var stat_b = parseValues("stat_b"); | ||
Line 61: | Line 61: | ||
==== parseValues ==== | ==== parseValues ==== | ||
Place this at the start of your script block, and you'll be able to use it in all your sheet workers. | Place this at the start of your script block, and you'll be able to use it in all your sheet workers. | ||
− | <pre> | + | <pre data-language="javascript"> |
const parseValues = (values, stat, type='int') => { | const parseValues = (values, stat, type='int') => { | ||
if(type === 'int') return parseInt(values[stat],10)||0; | if(type === 'int') return parseInt(values[stat],10)||0; | ||
Line 69: | Line 69: | ||
</pre> | </pre> | ||
By default, it returns an integer. If you call it with a second parameter, it will return either a float or a string: | By default, it returns an integer. If you call it with a second parameter, it will return either a float or a string: | ||
− | * parseValues(values, stat) or parseValues(values, stat, 'int') - returns an integer. | + | * <code>parseValues(values, stat)</code> or <code>parseValues(values, stat, 'int')</code> - returns an integer. |
− | * parseValues(values, stat,'float') - returns a Float (a number that is not an integer) | + | * <code>parseValues(values, stat,'float')</code> - returns a Float (a number that is not an integer) |
− | * parseValues(values, stat, 'str') - returns the value as text. (Not really needed!) | + | * <code>parseValues(values, stat, 'str')</code> - returns the value as text. (Not really needed!) |
This function does handle variable attribute names. If you were in a loop and creating attributes like, '''"stat" + i''' it will work fine. | This function does handle variable attribute names. If you were in a loop and creating attributes like, '''"stat" + i''' it will work fine. |
Revision as of 14:35, 7 February 2020
Contents |
Auto-calculating Attributes
Example 1
(credit: Rabulias)
Your best bet would be to avoid the autocalc fields entirely if you can. Monitor the two other fields and when they change, have a sheetworker that adds them up to the new value. Then you can refer to the new value in other calculations much easier.
on("sheet:opened change:stat_a change:stat_b", function() { getAttrs(["stat_a", "stat_b"], function(values) { setAttrs({ "foo_modchars": parseInt(values["stat_a"],10) || 0 + parseInt(values["stat_b"],10) || 0 }); }); });
Example 2
(credit: GiGs)
I remember seeing a script someone wrote to allow you to use autocalc fields within sheet workers, but it's just simpler to use Rabulias's approach(see example 1 above).
Add the relevant stats to the on(change:) line, and duplicate the calculation within the sheet worker.
I generally don't put my working in the setattrs call, but before it so i can more easily check it. Something like
on("sheet:opened change:stat_a change:stat_b", function() { getAttrs(["stat_a", "stat_b"], function(values) { var stat_a = parseInt(values["stat_a"],10)||0; var stat_b = parseInt(values["stat_b"],10)||0; var output = stat_a + stat_b; setAttrs({ "foo_modchars": output }); }); });
Helper Functions
This section is for useful functions that aren't complete sheet workers, but are useful to use in sheet workers.
Function: parseValues
(credit: GiGs) Many sheet workers have a bunch of lines like this:
var stat_a = parseInt(values["stat_a"],10)||0; var stat_b = parseInt(values["stat_b"],10)||0;
You might also have lines like this:
setAttrs({ "foo_modchars": parseInt(values["stat_a"],10) || 0 + parseInt(values["stat_b"],10) || 0 });
It gets tedious typing out all that. With the function below, you would instead write them as:
var stat_a = parseValues("stat_a"); var stat_b = parseValues("stat_b"); setAttrs({ "foo_modchars": parseValues("stat_a") + parseValues("stat_b") });
I think that's a lot easier to read. Here's the function:
parseValues
Place this at the start of your script block, and you'll be able to use it in all your sheet workers.
const parseValues = (values, stat, type='int') => { if(type === 'int') return parseInt(values[stat],10)||0; else if(type === 'float') return parseFloat(values[stat],10)||0; else if(type === 'str') return values[stat]; };
By default, it returns an integer. If you call it with a second parameter, it will return either a float or a string:
-
parseValues(values, stat)
orparseValues(values, stat, 'int')
- returns an integer. -
parseValues(values, stat,'float')
- returns a Float (a number that is not an integer) -
parseValues(values, stat, 'str')
- returns the value as text. (Not really needed!)
This function does handle variable attribute names. If you were in a loop and creating attributes like, "stat" + i it will work fine.
See Also
- Sheetworker Examples for Non-programmers
- Universal Sheet Workers
- The RepeatingSum Function
- How to integrate table of stats into a sheet