[Request] Stop values when reached to minimum/maximum
Request
Hi,
I have request about limitation of the value of MMF2.
Can you auto stop the increase/decrease all values when it reached to minimun (-2147483648)/maximum (2147483647) (note;exclude fixed value.)?
When value is over 2147483647 suddenly it will change value to -2147483648 and it will cause any problems.
Could you implement this method in MMF2 or MMF2.5?
I don't think you can change a data type at runtime in any programming languages: It's usually hard-coded. Popcap (a really well-known game developer (ever heard of Bejeweled, Bookworm, Typer Shark, or Plants Vs. Zombies?)) has acknowledged that they have to have a fixed limit (they've mentioned such a limit on the score in their games on their support site before, though I can't seem to find it at the moment), so I think it's a limitation of coding in general.Originally Posted by ASD
happygreenfrog this has nothing to do with changing data types at runtime and in fact is perfectly possible.
Working as fast as I can on Fusion 3
In my opinion, it would be difficult to implement. Firstly because it's the way binary logic works, so working in different way will imply to work differently from hardware (or put a layer on top of it). Secondly if you are trying to create some custom specifications, it will usually be expected to have the same behavior on all operators and functions, even not-Clickteam objects. At the end, I think that we will rely on some specification that cannot be garantee.
Ouly I think this request is just for Alterable Values/Global Values.
Just adding this behavior to add/substract from alterable/global values is less problematic to implement, indeed.
But mathematically speaking, I still don't like this option. When one overflow occurs, you know the amount of data you have lost, when you are saturating a value it starts to be harder to handle. For example, think about a counter already at 2147483647, add 10 to it and then remove 100. If the counter is overflowing you will obtain the right result at the end, but if he's saturating you will obtain something completely out.
So here is another proposition: remove MMF weak-typed alt./global values behavior, add an action to set the type of a value and then let the programmer explicitly choose between integer, float or integer counter type.
Add to Global Value A: Min(2147483647-Global Value A, valtoadd)
Subtract from Global Value A: Max(Global Value A-2147483648, valtosub)
That doesn't work when the wraparound happens multiple times and looks like it didn't actually wrap around at all.
Posting Permissions
Reply With Quote