The clock functions you wrote are using Millisecs() and we can't use that for a clock since everyones computers run at different speeds.
I disagree - The Millisecs() function should run consistently enough on all computers, as it is measuring the passing of time - A clock which deducts itself after each second should run at virtually the same speeds on any computer, otherwise if you had a fast computer, you may need to change the line
If LastTimeChange + 1000 < MilliSecs()
to
If LastTimeChange + 1010 < MilliSecs()
to achieve a 'true' second, but this obviously isn't done in practice. If there is any difference, it would only be negligible, so I wouldn't worry about it.
Looking at the DrawText function, would I just have to replace
Text x, y, string
with
DrawText.TypeText(string, x, y)?
If not, could you make the necessary alterations please?
Yes, the coding conventions...I personally think they can cripple the flow of the project if adhered to strictly - Of course, having the convention will help make writing the documentation easier, but I think we should focus more on actually creating something to document than worry about syntatical details. I'll correct any inconsistencies later on.
Thanks for making a start with the BVM, if we can interpret a single movement command and script the AI for a robot using just that command, that would be a great start. Follow that up with rotation commands such as Left(angle) and Right(angle) so that we get user-defined movement on the screen, and I think that would deserve an updated demo.
Ryan