Quote Originally Posted by 21o6
i don't really like the idea. there's no real benefit except i don't have to write
like what, 10 lines of code? it seems to me that the drawbacks weigh much
heavier than the benefits.
-> how do i write my own handler now?
Sorry, but I think you are aiming your arrows to the wrong target. This change is not my choice, but Wintermute's (the guy that created libnds).

-> why is x increasing, y empty and px/py now lacking any precision, which
they had before? (I still don't know how to calculate the correct values,
a simple div16 doesn't really do the trick but that's not the problem here).
I don't know. I got similar issues with emulators, while the same code worked as expected on real hardware.
-> "it's a lie". the arm9 can't communicate with the SPI, but the library
fools you in believing it can.
The way the lib works is: every VBlank, arm7 reads the input device state and stores them in the IPC struct in the shared memory. On the arm9 you can find some useful functions that read that shared memory. The arm9 can't communicate with the SPI, but can read the shared memory. The arm7 default code does the trick.
so ... how do i write my own handler, which gives me correct results,
which i actually expect? i don't care about that as long i can write
my own one (and pass stuff via IPC, which doesn't seem to work anymore,
because i can't even pass a simple 1 via ipc^.touchx, for example.)
Let me investigate a bit about that
i really appreciate your work and effort (i wouldn't be here without you
and wouldn't code my nds without you ), but this really really reminds
me of "it's not a bug, it's a feature" ...
In fact, as you guess, it's not a bug, it's a feature