Non lagacy version

Please excuse if this is in the wrong forum and move if necessary.

In reviewing the posts over the weekend (MMF2 must be popular by the sheer number of posts) there are a lot of questions about features, to which the answer is that the feature is that way for backwards compatibility with MMF1.5.

I was just wondering was it ever considered to dump the compatibility. I realise that a lot of people have legacy projects, (I have been a user of click products since the last century!) but they could have continued to use MMF1.5 for those. I know that when a major update comes along I tend to look at the new features and see how they could be used. This generally leads to re-creating most things (for the better), if not I would leave the project in MMF1.5 as it is obviously finished. Since the end result is usually an executable file it makes no difference to the end user what is was made in.

It’s just a thought, but if you were considering it I would throw my hat into the ring for an 'all new features enabled, but may limit compatibility' version.

Also I am sure that new users would have preferred a version that was designed to be the best it could. For example full 360 directions in the frame editor rather than 32.

Of course I am probably in a minority here, I was just curious to what would have changed if MMF1.5 was ignored (apart from the concept).

Please excuse if this is in the wrong forum and move if necessary.

In reviewing the posts over the weekend (MMF2 must be popular by the sheer number of posts) there are a lot of questions about features, to which the answer is that the feature is that way for backwards compatibility with MMF1.5.

I was just wondering was it ever considered to dump the compatibility. I realise that a lot of people have legacy projects, (I have been a user of click products since the last century!) but they could have continued to use MMF1.5 for those. I know that when a major update comes along I tend to look at the new features and see how they could be used. This generally leads to re-creating most things (for the better), if not I would leave the project in MMF1.5 as it is obviously finished. Since the end result is usually an executable file it makes no difference to the end user what is was made in.

It’s just a thought, but if you were considering it I would throw my hat into the ring for an 'all new features enabled, but may limit compatibility' version.

Also I am sure that new users would have preferred a version that was designed to be the best it could. For example full 360 directions in the frame editor rather than 32.

Of course I am probably in a minority here, I was just curious to what would have changed if MMF1.5 was ignored (apart from the concept).

drop support for MMF 1.5? get out
drop support for TGF 1, KnP and all that, in the next MMF (2.5?) drop support for 1.5 and only have support for MMF (2.5?) and 2.0 files

drop support for MMF 1.5? get out
drop support for TGF 1, KnP and all that, in the next MMF (2.5?) drop support for 1.5 and only have support for MMF (2.5?) and 2.0 files

Most of the features were not ignored because of backwards compatibility. If this were the case, we wouldn't have most of the features we do. Things such as 32 directions were done mainly because the default movement is based on 32 directions. The reason it wasn't upgraded to 360 directions (at least I think) is because MMF2 has the capability to rotate in 360 degree angles at runtime already.

Dropping MMF 1.5 compatibility would have done nothing to improve MMF2, mainly because it's not the backward compatibility that's messing with MMF2, its the fact that MMF2 was designed from the ground up by 2 developers. There was bound to be glitches and major suggestions when the program was finally released. The only reason MMF2 DOES have the backwards compatibility it does, is because all the features from MMF 1.5 exist in MMF2. This allows MMF2 to reproduce anything that MMF 1.5 could.

In proof of this compatibility issue is, anything sent from MMF 1.5 over to MMF2, is NOT capable of returning back to MMF 1.5, because of compatibility issues. Now when you start trying to keep THOSE methods of compatibility alive, that is when you have problems. That is not the case here however.

Most of the features were not ignored because of backwards compatibility. If this were the case, we wouldn't have most of the features we do. Things such as 32 directions were done mainly because the default movement is based on 32 directions. The reason it wasn't upgraded to 360 directions (at least I think) is because MMF2 has the capability to rotate in 360 degree angles at runtime already.

Dropping MMF 1.5 compatibility would have done nothing to improve MMF2, mainly because it's not the backward compatibility that's messing with MMF2, its the fact that MMF2 was designed from the ground up by 2 developers. There was bound to be glitches and major suggestions when the program was finally released. The only reason MMF2 DOES have the backwards compatibility it does, is because all the features from MMF 1.5 exist in MMF2. This allows MMF2 to reproduce anything that MMF 1.5 could.

In proof of this compatibility issue is, anything sent from MMF 1.5 over to MMF2, is NOT capable of returning back to MMF 1.5, because of compatibility issues. Now when you start trying to keep THOSE methods of compatibility alive, that is when you have problems. That is not the case here however.