"Apply Changes (Ctrl + Enter)" being too smart..

When clicking "Apply Changes (Ctrl + Enter)" below the script editor, nothing happens if the script has not been changed manually.

This is somewhat annoying when you use external scripts or you're debugging a script that behaves non deterministic due to changing random values or similar. While a script ultimately should behave deterministic, it is not always so when you're working on it - certain values might cause invalid table lookups etc, but in the next "try" things might work just fine.

As it is now, I often find myself triggering changed state by making line breaks, spaces etc. so I get a reaction when clicking the "Apply Changes" button.

Clicking "Apply Changes" should blindly force a fresh reevaluation, without regard to script editor activities..

Perhaps, I was not sure - I ended up posting it here because clicking "Apply Changes" will not always apply changes.. you decide

Yeah, as I think of it, a change has occurred is when the output of a succeeding rendering is not similar to the previous..

Here is a simple boiled down version of the problem:

function prepare()
v = math.random()
end;

function get_sample(x, y)
return v,v,v,1
end;

This will produce different output each time it is rendered, but the current FF mechanism for changed status will not catch this.

Now I consider such a construction wrong, because I should have added a
math.randomseed(VARIATION) to the start of prepare..

But that is exactly the point: how will I know this is wrong when FF don't rerender the output? The current behaviour of "Apply Changes" leads me into a false conclusion that the output is consistent..

(you need to change the script with linebreaks or similar to force changed status)