- Joined
- Nov 8, 2014
- Messages
- 130
- Mac
- Classic Mac
- Mobile Phone
Yes, that's very annoying. There seems to be some strange messages coming from touch screen. Probably these could be filtered out easily. I was travelling couple of weeks so I haven't done anything related to this project lately.
My to-do list currently is something like this:
- General: Setup remote GDB debugging to cube i7. Yesterday I tried and failed doing this. Problem is that gdbserver is not available from macports.
- Wifi: Use GDB and Hopper disassembler to see why RtWlanU.kext is crashing. There is probably nothing that I can do here but I want to try debug this.
- HID: Filter out garbage events
- HID: Unpack HID multitouch events and construct them as mouse events (emulate mouse scrolling etc.)
- HID: Fix stylus pressure issues
- HID: Disable touch screen when stylus is used. Currently it's impossible to draw anything because accidental events coming from palm touching the screen.
I will chalk these so-called garbage events down to general instability and poor code in VoodooI2C in general. I think once I (or someone else) gets round to completely organising, commenting and refactoring the code, we will see greater stability in the touch devices. I think the fact that we are polling for input as opposed to using the built in interrupts is also a factor (we have to manually set the polling rate on a device-per-device basis, that can't be good for stability). With regards to palm rejection, is the stylus a separate I2C device or are they two HID devices that report from the same i2c-hid device? If its the latter than palm rejection should be pretty easy.
In any case, I'm looking forward to seeing your contributions to the code base soon