The summary API was created with the intention of being lighter-weight compliment to the events API for users that don't care about the high-polling rate and just want a simple "is a pen interacting? where is it? what buttons are pressed?" kind of API. However, as shown in the updated eframe-viewer, this logic is only ~200 lines long to implement as a user and drastically simplifies the backend at no loss of generality.
The summary API was created with the intention of being lighter-weight compliment to the events API for users that don't care about the high-polling rate and just want a simple "is a pen interacting? where is it? what buttons are pressed?" kind of API. However, as shown in the updated eframe-viewer, this logic is only ~200 lines long to implement as a user and drastically simplifies the backend at no loss of generality.