I've found that the example based on variables I've used for my previous example actually doesn't matter for the essence of the problem. The problem remains even if using
absolute numbers in the range option. For instance:
Gui Add, Progress,
w50 h20 cBlue backgroundyellow vProgbar ;<--- bar width = 50 pixels
GuiControl ,,progbar, range
1-50 ;<--- in this case, each bar
PIXEL should be a bar "
unit" of its
progress
Gui show
GuiControl ,,progbar,
50 ;<--- does not progress to the
END of the bar, but to its
middle ?!? :/
GuiControl ,,progbar,
1
GuiControl ,,progbar,
+25 ;<--- also does not progress to the bar's MIDDLE (since its range is 1-50) but to "a quarter" of the range
It seems indeed the number (or variable content) we pass to the positioning is never
according to the range but is
always a "
percent" of the range...
so my question remains: why there has a
range option for this control since we always have to use
relative positioning ("%" of bar length), never can use
absolute numbers for the positioning? :/
other: let's say you have 1000 lines of a text file to read into a var. If we set the
range option to "0-1000"... we CAN'T use "
+1" for progress of
each line that was red. Because the value is "relative" to the bar range, not absolute in its range. We'd have to use a formula :/ to the progress value (in this example, it could be: #linesred/1000). Because "+1" in this example would mean
TEN lines red (+1"%" of 1000) - not one line...
So, again, why there'd have an option for "ranges" since the value for the positioning seems is always "relative"/"%" to the bar lenght
despite its range that was set..? :/
