Home/ Questions/Q 95617
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-10T23:41:10+00:00

Here’s the basic idea: There is a java window (main) that opens another java

  • 0

Here’s the basic idea:

There is a java window (main) that opens another java window (child). When the child is created, part of the initialization sets the focus in the appropriate text field in the child window:

childTextField.requestFocusInWindow(); childTextField.setCaretPosition(0);

The child is generally opened through a serious of keystrokes via a command line type interface. When the window is requested, 90%ish of the time, the focus correctly goes to the child window text field and the user can type in the box. If the command to open the child is sent off (with a press of the enter key) and the user immediately starts typing before the new window is created, the text is correctly buffered and appears in the new textfield after the window opens.

However, every once in a while when the user requests the child window to open and then starts typing, their text does NOT appear in the text field. Only after they click with the mouse in the field does the text they have typed appear. It’s like it’s being stored somewhere and doesn’t come out until they click.

The real frustrating thing here is that I can’t seem to reliably reproduce the issue at all. It definitely happens, but not regularly enough to debug nicely.

There is of course all kinds of other mojo going on behind the scenes, including communication with a server app, but I’m not convinced it’s related.

Any thoughts or ideas would be very much appreciated.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. On first look, that sounds like it might be a bug in the implementation; the key should be in the same event queue as the mouse events. There’s another issue possible though: the event queue is running in a thread separate from the program main; without knowing what’s going on in the rest of the application, it’s tempting to wonder if the event queue thread is getting blocked somehow.

    Actually, the difficulty you’re having with reproducing it makes that sound even more likely.

    Debugging that case will require a little craft and trickery. If you’re on Solaris 10 or OS/X, I’d recommend using dtrace; you can easily put a trace point on the event queue. In not, you might want to have another thread that periodically drops something on the event queue.

    • 0