![]() So you will have "frozen" keyboard/mouse input for that duration. If the winhook callback is not handled in a timely fashion, the input will not be passed on to other applications, as Mumble needs to process it before it's passed on. When winhooks are enabled, the hook callbacks are processed on the same thread in which we poll DirectInput for state changes. So, when you run with winhooks enabled, it locks up all your input devices on the machine? Not just once, but multiple times?ĭoes it lock them up for around the same amount of time that it takes for your PTT to change state when they're disabled? (The issue you created this ticket for.)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |