> As you can see, I misspoke earlier: the events have *exactly* > the same time > field. Combining this with what I said about the queuing > (the "atomic" > insertion), I think you'll agree that doing XPeekEvent inside the > KeyRelease handler, and discarding the pair of events if the time, > keycode, etc fields match, is a sufficiently robust test. > > Also, though this may seem nasty, it is nice in the sense that all > programs reacting to KeyPress events get key the same key repeat > behavior 'for free'.
Well that's good news. Everything should be doable then. To bad about no per-app turnoff tho. Thanks a lot! I should have this thing (alternative tagging interface) done soon, then I will post.
