In programming I'm not just a beginner, in hardware programming I am!
And this may relate to many RobotC users.
Please recall: what may be the reasons to anyone for buying RobotC?
To me it was (and would probably be for most of others):
- do anything what's possible with NXT-G, but in a script language
- do it quite easily like NXT-G, but in a script language
- do it similar to NXC or pbLua, but with more features
- if you need help, you'll get it like by the NXC or pbLua developers, but more, easier, and faster
- get access to anything that can be attached to the NXT, and don't have to worry about technical details: just plug and play!
Using a NXT-G block, you don't have to think about any I2C connections, failures, value checking. You plug it and it works. That way RobotC driver routines should work, too. If anyone wants to program "machine-oriented" he might do it - but he must not have to do it. (Like programming Windows applications: I want to write a program, and I don't want to think about how to draw a form, a button, a panel, or a drop down menu, and how to erase it and free the memory).
So please give us easy-to-use interfaces to any third party sensor (like the compass sensor driver by Hitechnic that I posted) and don't let us crush our heads thinking about I2C.
By the way: the pbLua developer even speaks German and posts and gives help in a German Mindstorms forum!