Xenoamor

Results 16 issues of Xenoamor

This would be handy for those of us who only want the merged screen

Is the following code still necessary? https://github.com/kanflo/opendps/blob/bc665f3840c12b66808b7b3f871b2935865f60a9/opendps/hw.c#L290-L298 I have the impression that this is now not needed as any device calibration should account for this. It also causes the ADC...

Any ideas how the following code compiles? https://github.com/kanflo/opendps/blob/c1a8ab69d97ee3a329a2283ec88c49150537978c/opendps/uframe.h#L44 https://github.com/kanflo/opendps/blob/c1a8ab69d97ee3a329a2283ec88c49150537978c/opendps/uframe.h#L47-L52 https://github.com/kanflo/opendps/blob/c1a8ab69d97ee3a329a2283ec88c49150537978c/opendps/protocol_handler.c#L348-L351 I've never seen `uint8_t buffer[variable];` compile before

We should look into using fixed point arithmetic as it will be significantly faster and reduce our required ROM space

The current gradient detection algorithm does not work correctly in a noisy environment as discussed #120 ![image](https://user-images.githubusercontent.com/7109951/53038781-76c5c000-3475-11e9-9bc8-18ded9071039.png) This should be improved to prevent incorrect calibration

As discussed in #103 a method of fetching/retrieving the calibration coefficients from the original DPS firmware would be very useful

It could be interesting to have a graphing screen. Something like this: ![graph_dot](https://user-images.githubusercontent.com/7109951/51086372-1d63c600-173e-11e9-9b32-db6b4972782f.png) ![graph_vector](https://user-images.githubusercontent.com/7109951/51086373-1dfc5c80-173e-11e9-838b-85b3bd8ef187.png)

Changing between screens with different layouts leaves what was previously drawn on the screen in the background. I could be wrong about this but I believe this would be because...