Quote Originally Posted by Taz View Post
Perhaps I am missing your point on this ...
The calibration data shown on the screen is read from the bin image and stored in each of the calibration controls.

Let's assume there are two calibrations defined that use the same memory location like this:
B1111 is a calibration stored in a single byte.
B2222 is a user's cax definition which is also stored in a single byte at the same memory location as B1111.

When EFILive loads the file it reads the value at the shared memory location, lets say it is $55 and copies the value into B1111 and B2222, so they both start with the same value $55.

Now you change B1111 to 77. B2222's value will not change it will stay at 55. Then you go and change B2222 to 33, B1111 won't change, its value will remain at 77.
When the file is saved, both B1111 and B2222 are stored back into the binary image because they were both* modified.
Anyway, because V7 was never designed to handle overlapping calibrations, you can never know which calibration will be written back to the file first.
If B1111 gets written first, then B2222 gets written after it, then the file will contain B2222's value of 33.
If B2222 gets written first, then B1111 gets written after it, then the file will contain B1111's value of 77.

Next time you load the file both B1111 and B2222 will again have the same value, but the value ($33 or $77) will be determined by what happened during the previous file save operation.

* If one of the values was not modified, then its value would not be written back to the binary image so there will be no contention - but the software cant rely on the user "not doing something". There's already a bunch of "double checking" code that handles problems caused by the VVE implementation because multiple VVE tables can update the same base coefficients tables (i.e. overlapping). If multiple VVE tables are open and modified when the file is saved, the user is asked to close them and by closing them the user is forced to decide which of the multiple, open VVE tables gets applied to the coefficients table prior to saving the file. Right now developing an equivalent, generic solution for overlapping *.cax calibrations is not a high priority. It is something that we will address in the V8 editor.

Regards
Paul