exit process loop after sucessful input

[andr-ew]

(input that passes through both the filter and the handler)

this allows alternate functions in the common input space

yea on second thought I believe this would be more complicated - basically I think the handler would need to be called every time for all affordances but update would only happen for the highest z sorted affordance, all other handler args would be tossed. easiest way to do this would be an additional update loop & storing hargs between

[andr-ew]

closing 4 now - better solutions for current issue & I think this is out of scope / ultimately opinionated vs. current behavior