Rename `markerchanges` event, now that we support non-markers #94
Now that we support Image targets alongside markers like barcode/qrcode (and, anticipating even more crazy target types in the future), we should set appropriate names for events fired from the toolkit.
Do we want separate events for each target type? Or one event for any result changes?
Today we use
...also, right now this event fires when some target is found, yet we don't have any results for it.
This ends up with found:  and lost: , which seems pretty useless.
Now that we use a global variable to store the actual string value, we could use:
And possibly use the longer name for the actual value. I doubt anyone is using