I really like your idea of using the numpad + to switch between fields. That frees the other hand for handling the paperwork. A great speedup!
To avoid lag slowing down entry, I can do all checking and db-to-entry comparisions asynchronous. They're done via sockets anyway. As for proof checking as a second persons job, we'd need two or three people for every one person entering stuff. Printouts would be too slow, but because there's a networked database solution existing already, proof reading could be done on another computer. I was thinking more about how to avoid false entries to begin with. Some stuff can be checked while entering via the DB, but other stuff just can't, unless all four players from a table have been entered. That is why I was thinking about forcing the person who enters stuff to also recheck it in a dialog... but that is probably just not speedy enough. I wanted to show a kind of fake table on the screen, showcasing what each of the four players have entered, making a noise or red error message when stuff does not match up. Now that I think about it, that also ensures errors will have a very high probability of being found and fixed if they where entered wrongly for the first player. So most likely no one actually has to manually double check entries, and everyone can just type away as fast as possible. On 22.07.2012, at 17:13, Mike Bonner wrote: > A method that might work is to use + to switch between fields (like adding > numbers on a calc) then enable the "add" button when all fields are full, > activated by the enter key. > > An additional thought I had was to have a 2nd person for proof check. > (maybe hire the first from a temp agency with the required skills because 1 > person who is really good will likely do a better job than 3 or 4 who don't > have the practice) If you can get your hands on a dymo label printer that > spits out a label containing the just entered data as a type of "receipt" > that is tacked to the original note, the 2nd person can verify and fix an > error if one does occur. -- Use an alternative Dictionary viewer: http://bjoernke.com/bvgdocu/ Chat with other RunRev developers: http://bjoernke.com/chatrev/ _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
