Closed geogauci closed 9 years ago
see #8.
I replaced the keyboard, and it magically started working! Unfortunately I'm getting the same issues engst03 (#8) is getting. Probably while the first ctrl-alt-del is being processed, the second one will not be intercepted. Any ideas how to go around the problem? My first though would go to multithreading, but this would probably introduce problems of its own, so any other suggestions would be very appreciated!
The suggestion I give is to build a simple sample that would show you the characters being typed and figure out the cases the broken sample is failing to catch. I guess this is the problem, the logic is failing to catch a valid ctrl-alt-del sequence the system interprets as valid, but the sample ignores.
To simple check it's able to block ctrl-alt-del, you may just disable one of the keys (ctrl or alt or del) through it, so ctrl-alt-del would never be able to be produced. If it does block CAD through this proof-of-concept, then the problem is a matter of interpreting all cases the system captures CAD and intercept it.
I'm currently testing the cadstop sample, trying to intercept the ctrl-alt-del sequence, but it's not working for me. Keypresses are being caught, but not the ctrl-alt-del sequence. Seems like stroke_sequence array is being filled by the same key (ctrl). Any ideas?