Alejandro Guizar wrote:
Yes, it won't. However, what I wanted to point out with my extract from ScopeInstanceImpl.setVariable is that it ignores the historyEnabled parameter if the variable already exists. I do not know whether it makes sense to enable/disable history for an existing variable. In any case that would be a feature request that we can defer for the time being.
Fair enough, just wanted to make sure we are on the same page, so to say.
Agree that we could make further enhancement later on.
Will you make any other changes or shall I commit history stuff as well?