Changing globals by index crash

[Blake]

I was trying to figure out a crash in my project, and it seems to happen when changing a global by index, when the index is zero.

I've uploaded a sample application to show the problem.

http://bledwards.googlepages.com/globalscrash.rar

[Blake]

I was trying to figure out a crash in my project, and it seems to happen when changing a global by index, when the index is zero.

I've uploaded a sample application to show the problem.

http://bledwards.googlepages.com/globalscrash.rar

[Yves]

Ah sorry. The crash should be fixed in build 242. (but the index of the first global value is 1, you should not use 0)

Yves.

[Yves]

Ah sorry. The crash should be fixed in build 242. (but the index of the first global value is 1, you should not use 0)

Yves.

[Blake]

Ok, cool. I found that the first one was 1, not 0.. although in the application properties it lists the first value as 0. Also when making the expression it says that the result should be between 0 and 26 (or however many globals you have).

[Blake]

Ok, cool. I found that the first one was 1, not 0.. although in the application properties it lists the first value as 0. Also when making the expression it says that the result should be between 0 and 26 (or however many globals you have).

[Yves]

Hmm... we'll change this text.

I've verified the routine in MMF 1.5, it was working due to an horrible bug... In fact setting the global value 0 via an expression in MMF 1.5 was writing the value into the global value 16. Hopefully the fix in MMF 2 won't cause compatibility issues with 1.5 applications that are using this function with 0-based indexes.

Yves.

[Yves]

Hmm... we'll change this text.

I've verified the routine in MMF 1.5, it was working due to an horrible bug... In fact setting the global value 0 via an expression in MMF 1.5 was writing the value into the global value 16. Hopefully the fix in MMF 2 won't cause compatibility issues with 1.5 applications that are using this function with 0-based indexes.

Yves.