Will deferring the emit() call work?
#Setting input as handled blocks signal
raw badge
raw badge
wow
just to be sure you should run this in a new scene or even project with minimal newly created scripts to make sure theres not any error outside that snippet leading to this
i'd still assume this is "intended" behavior and not a bug. but you probably need to search and if nothing comes up post on github
i guess its possible that this combination of signals ( your custom signal ) within signals ( built-in input event signal ) and the blocking of other signals triggered by the input handled during that signal may need some built-in pre-checks and specific strict handling of whats possible to execute in this context
so that it's technically not a bug, but even if "intended" still not something thats obvious to user or even documented
if i had to make a case why it isnt a bug.. and just guessing because i dont know the source code well enough
that one surprised me too
thats why i think its the best option to take this to github where actual engine coders/understanders can untangle this one
sure. and please leave a message here if you find out or a link to an issue you post 😉 curious to see whats behind it
raw badge
interesting..