precedence in multi parameter windows?

[BabaG]

i use xnview to correct a single image from a batch. i make note of the
settings applied to the single image, write them into a script, and run
nconvert from the script, applying the xnview-derived values to many
images.

i understand that nconvert applies the changes i make in the order they
are written in the script. how does xnview handle it's corrections, particularly
when they are applied from a multi-parameter control window like :

brightness/contrast/gamma/balance

if i were to, say, correct red, then gamma, then red again, then gamma again,
then red again, then gamma a last time, would i have to go through that
same sequence in my script? or could i just take the cumulative values
displayed in the window and apply that to my script?

i ask this because i've recently had some things come out differently than
i expected and believe this precedence to possibly be the issue.

i'm thinking i should adjust my script to make sure it processes images in
the same order that xnview handles it's adjustments.

and what if the values being manipulated are not in the same window? an
example would be to adjust the red, close the window, open
hue/lightness/saturation, adjust saturation, then continue toggling back
and forth between the color window to adjust the red and the hls window to
adjust the saturation. how would one quantify the adjustments when made in
this, rather intuitive, manner?

it might be nice to have an option to retain the original, relative values (or
would they be absolute?) until a final commitment was made on all values
together. that, along with an summary of the adjustments that had been
made would be very helpful for this kind of work.

where i believe it's most evident is when gamma and level adjustments are
made and toggled with color adjustments. some kind of running tally for
this would be very helpful.

thanks,
BabaG