 | | Blocking SetUserDisplay?
|
|
I have a program with a setup routine for calibrating light sensors. During the setup routine, it does: SetUserDisplay (a, 2); Then in a loop, reads the values of 2 light sensors into x & y, averages the readings and then does: a = x * 100 + y; to (...) (19 years ago, 4-Jun-05, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Blocking SetUserDisplay?
|
|
(...) That's the only way around it as far as I know. JB (19 years ago, 4-Jun-05, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Blocking SetUserDisplay?
|
|
(...) You may be able to work around this by using parenthesis (untested). a = ((x * 100) + y); or you might try a = 0 + ((x * 100) + y); John Hansen (URL) (19 years ago, 5-Jun-05, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Blocking SetUserDisplay?
|
|
(...) Neither of these work, although the second one does introduce a temporary for everything except for the 0 part. It will result in the display sometimes showing a value of zero. NQC tries really hard to use as few variables as it can so you (...) (19 years ago, 5-Jun-05, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Blocking SetUserDisplay?
|
|
(...) Thanks for the ideas! Actually these yielded some interesting results: a = 0 + ((x * 100) + y); occasionally yielded 0 (as expected), but never yielded anything other than 0 and the correct value (that I saw). a = ((x * 100) + y); and a = (x * (...) (19 years ago, 5-Jun-05, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Blocking SetUserDisplay?
|
|
(...) In C you would declare a as volatile. Jürgen (19 years ago, 11-Jun-05, to lugnet.robotics.rcx.nqc)
|
