--- xdocs/changes.xml (revision 1839678)
+++ xdocs/changes.xml (working copy)
@@ -257,6 +257,7 @@
- 62211Fix HTTP Request Server Documentation. Contributed by orimarko at gmail.com
- 388Fix a typo. Contributed by Giancarlo Romeo (giancarloromeo at gmail.com)
+ - 62446Counter documentation is wrong in required fieds. Contributed by orimarko at gmail.com
General
--- xdocs/usermanual/component_reference.xml (revision 1839678)
+++ xdocs/usermanual/component_reference.xml (working copy)
@@ -4236,10 +4236,10 @@
Descriptive name for this element that is shown in the tree.
- The starting value for the counter. The counter will equal this
- value during the first iteration.
+ The starting value for the counter. The counter will equal this
+ value during the first iteration (default 0).
How much to increment the counter by after each
- iteration.
+ iteration (default 0, meaning no increment).
If the counter exceeds the maximum, then it is reset to the Starting value
.
Default is Long.MAX_VALUE
@@ -4248,9 +4248,9 @@
If there is a problem interpreting the format, then it is ignored.
[The default format is generated using Long.toString()
]
- This will be the variable name under which the counter value is available.
+ This will be the variable name under which the counter value is available.
If you name it counterA
, you can then access it using ${counterA}
- as explained in user-defined values
+ as explained in user-defined values (By default create an empty string variable that can be access using ${}
)
In other words, is this a global counter, or does each user get their
own counter? If unchecked, the counter is global (i.e., user #1 will get value "1
", and user #2 will get value "2
" on
the first iteration). If checked, each user has an independent counter.