08-17-2020, 02:44 PM
Hi,
Here is some context, and after that I answer directly your questions:
That's some very old Curvy version. If not done already, make sure you read the release notes so you don't miss any new feature.
After aquiring Curvy on 2018, one of the things I worked on is to simplify the API. There was too many public methods which were basically a one liner calling another public method. I removed (and still removing) a lot of those methods to make the API as small and easy to use as possible.
Before releasing any breaking change in Curvy, I mark the API method that will change as Obsolete, while providing the new alternative. The Obsolete tag displays a compiler warning when compiling the code, and often I add to it a custom message saying what method to use instead. So for someone who updates regularly, and acts accordingly when seeing a compiler warning from Curvy, the upgrade is done smoothly. But for someone who had not upgraded for a long time, then this process becomes problematic. Ideally, the Unity asset store would allow owners of a specific asset to get all the older updates, so you could upgrade easily and gradually between consecutive versions, but this is unfortunately not the case.
Now the answers:
Here is some context, and after that I answer directly your questions:
That's some very old Curvy version. If not done already, make sure you read the release notes so you don't miss any new feature.
After aquiring Curvy on 2018, one of the things I worked on is to simplify the API. There was too many public methods which were basically a one liner calling another public method. I removed (and still removing) a lot of those methods to make the API as small and easy to use as possible.
Before releasing any breaking change in Curvy, I mark the API method that will change as Obsolete, while providing the new alternative. The Obsolete tag displays a compiler warning when compiling the code, and often I add to it a custom message saying what method to use instead. So for someone who updates regularly, and acts accordingly when seeing a compiler warning from Curvy, the upgrade is done smoothly. But for someone who had not upgraded for a long time, then this process becomes problematic. Ideally, the Unity asset store would allow owners of a specific asset to get all the older updates, so you could upgrade easily and gradually between consecutive versions, but this is unfortunately not the case.
Now the answers:
- MoveByLengthFast and other move methods were reworked and moved to the SplineController class. The closest thing you can find in recent versions is SplineController.SimulateAdvance (if you don't need events to be triggered while moving). Otherwise look at SplineController.Advance.
If neither of those help, I am sending you the old implementation of MoveByLengthFast, but it will not compile without modifications.
- e.ControlPoint.Connection.OtherControlPoints
- I am not aware of any change in the spline's data that is not backward compatible. Let me know if you find such thing.
Please consider leaving a review for Curvy Splines, this helps immensely. Thank you.
