- Component.getMousePosition() and KeyboardFocusManager.getCurrentKeyboardFocusManager().getActiveWindow() both always return null.
- This should be solveable/hackable, though I don't have a good solution yet.
- At the very least this should allow for MouseListener support, but doesn't make JTablet very useful
- The NSEvents are being mucked up in both Firefox/Chrome, and by the time they reach the JNI code, they're missing all the Tablet data.
- Both Firefox (since 3.6.4) and Chrome (since ever?) have out-of-process plugins, so it might be related to that.
- It's also possibly related to a recent update to the Java plugin.
- On Firefox, the x/y coordinates include decimal information, but nothing else comes through (pressure, tilt, etc)
- On Chrome, not even that comes through.
- On Safari with "in their own process" is the same as Firefox, except MouseMove events are not even fired!
My guess, when the app runs in its own process, Java is a separate NSApplication, and JTablet isn't getting the original events. When it's embedded in a browser window, the browser decides when to forward events to the separate process (losing data in the process).
I have no idea what to do about this. Somehow intercept the events at an OS level? Hi-jack the browser event stream?
Marcello