theclaw
Joined 9 years ago
Joined 9 years ago
I used to feel the same way. I’m only a casual linux user and I didn’t want to climb this particular mountain but having learned just a little about it, created some of my own units and played with the tools the sense of alienation dissipated and I was fairly happy with it.
Playing Kinect games was either frustrating because the game would not recognise your gestures, overly complicated because there were too many possible gestures and no obvious affordances to the user other than ‘move your whole body somehow’, or simply too physically difficult for some players to perform.
It’s ironic that such a high fidelity input device actually limits the kind of games you can design for it. Some of the best Kinect games were those that used the input data for purely cosmetic purposes.
That BASIC also had proper functions and procedures as well as special fast integer variables in zero page, it offered easy access to the whole machine from graphics to sound to ADCs and tape or disk IO. It was also very fast for the time, and the manuals that came with the machine were excellent.
The BBC micro user manual section on the inline assembler is available here for anyone interested in how it worked: http://central.kaserver5.org/Kasoft/Typeset/BBC/Ch43.html
The type of effect used to create these candy words is covered in the "Marble Sorting Machine" video https://www.youtube.com/watch?v=em-pVICrnqM
Perhaps the fingerprint reader returns a result of 0 for "valid print and not matched", result 1 for "valid print and matched", and result -1 for "not valid print". If the phone vendor code simply tests for a non-zero result code and treats this as "matched", then the situation described would occur.
It would be interesting to test with other smooth objects that might activate the reader.
testResult = TestFingerprint(fingerprint);
if(testResult)
return UNLOCK_OK;
else
return UNLOCK_FAIL;
to this: testResult = TestFingerprint(fingerprint);
if(testResult == RESULT_OK)
return UNLOCK_OK;
else
return UNLOCK_FAIL;