Hi Rob,
Thanks for getting back to me. It's really helpful to have deprecation information in the documentation as well as header files to give information even if just a hint on what API to use in it's place. Our app which has been using Shinobi for ages had a lot of deprecation warnings most of which had no information on how to implement the changes that we needed without these specfic APIs. We had to hook into some of the more advanced APIs to achive the features and look that we want.
It's impossible for us to keep track of every change release to release as we only work on our shinobi based apps when the client wants us too, so it's hard for us to be pro-active. Deprecations are really useful to see what is on it's way out, so knowing how to implement this required functionality with new APIs is essential.
Another method [SChartAxis __refreshDataRange] is throwing a deprecation warning, do you know how I should achive this action now?
Thanks.