If there are certain features you would like to have added to the 2.0 version of the suite, you can leave a comment at the end of this post. If it’s something that will be of use to others as well than I will consider implementing it. Now is a good chance to change parts of the API because I am not guaranteeing backwards compatibility with the 1.X version of the suite.
So let me know!
Hi I am a regular user of your sensor drivers, although I haven’t been keeping up to date recently so its possible some of these thing may already have been done.
1. I was going to ask for the ability to easily use non standard i2c addresses on mindsensors sensors, but I see that has already been done.
2. This may well not be worth the effort and complexity, But I found that when multi-threading on the NXT and using the API from different tasks (useful if you have a whole heap of sensors on different ports that you want to poll quickly) it always crashes the program because of variable conflicts.
Love your work mate
Thanks for reminding me about the I2C address thing. There are other sensors that I have not implemented this on yet.
As for making the API thread safe, I’m afraid I cannot do that. It’s not the effort, I’d love to make this possible, but there’s simply no way to do this safely in ROBOTC at the moment. As soon as you call a function from two places at once, you risk a collision of the arguments passed to it.
Thank you for the feedback, it’s really appreciated.