Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Great product! Documentation needs work!
#2
Hi

Thanks for taking the time to write this feedback.

Adding coding examples for simple tasks is a good idea. I will try to do that after finishing the version 8 release.

Right now, the way I was hoping people will learn Curvy Splines with is to look at the example scenes and their scripts. Then, using the documentation form curvyeditor.com for the editor, and api.curvyeditor.com for the api to know more about what they see in the example scenes. This does not invalidate your point, since it is best to have a page with just the relevant part of the code, rather than a scene that the user has to look into.

About the commonly used methods, their is a sentence at the top of that section that says "This applies for Curvy Spline". Did you miss that or was is not phrased properly (not stating the CurvySpline class)?

Feel free to share with me any enhancements you think about.
Please consider leaving a review for Curvy. This will help a lot keeping Curvy relevant in the eyes of the Asset Store algorithm.
Reply


Messages In This Thread
RE: Great product! Documentation needs work! - by _Aka_ - 08-26-2021, 06:47 PM

Possibly Related Threads…
Thread Author Replies Views Last Post
  GUILayout.TextField:s dont work with CurveySplines Mike Danielsson 6 12 09-01-2023, 03:38 PM
Last Post: _Aka_
Question How to modify Example 12 to work bi-directionally and more than 2 connected splines Mambosa 3 17 11-29-2022, 06:59 PM
Last Post: _Aka_
  How do waypoint collisions work? funkd 1 2,363 05-21-2019, 10:29 PM
Last Post: _Aka_
  Script inheriting SplineController doesn't work the same as adding component? clearleaf 1 2,177 04-28-2019, 12:41 PM
Last Post: _Aka_

Forum Jump: