Support |
Dear Jeff, in context of the discussion of changes from Möbius version 1.42 to 1.43, I have very mixed feelings about how these changes were implemented. First of all, a lot of users want (or need) forward compatibility. On the other hand, innovating a product (like software) sometimes requires to leave that behind. Often, manufacturers try to at least reflect that with the version numbers. So, my question is this: when you do changes (as in 1.43) which will result in a lot of stuff not working anymore (the "sus modes" we've discussed are but one example, another one is that for some reason, my track copy script no longer works, possibly because the behaviour of copy has changed?) - why not make a new major release, reflected in a version number like 2.0? That way, it is easily recognizable that while an update from e.g. 1.41 to 1.42 can be done by anyone without fear of consequences, an update from 1.42 to 2.00 may not. About the other discussions: 1) just tested the "auto reverse" script with the scope of the variable being track instead of global - great! 2) strangely, on 1.42, your adapted script (with the wait last statements) behaved exactly the same as my original version without those adaptions - well, I think exactly, because it was "deterministic chaos" ;). As I need to go back to 1.42 for the short term, I could try that again... Yours, Rainer -- http://moinlabs.de Follow me on twitter: http://twitter.com/moinlabs