Actually jay, you’re very nearly right. The trick is you must always ADD the new context before REMOVING the old context. As long as some context exists which is listening for the input, the option you described will function as desired. My mistake was thinking these two were interchangeable; I was removing the first context and then applying the second, but in so doing I evidently created a situation where, because nothing was listening to the input, it got reset. I would have assumed that as long as these function calls occurred on the same frame, it would be the same result, but it’s not. You have to add the new context, THEN remove the old context, so that some action that cares about the input is always active.
2 Likes