Nice catch! Looks like an event was initialized with a wrong flag. That'll be fixed in the next version.

Thanks for the report!