New JInternalFrame does not have keyboard focus

[Sciss]

When using internal frames and I open a new JInternalFrame, that new frame is visibly shown to have the focus (has the blue outline), but the keyboard focus is still in the previous component (e.g. the internal frame which had focus before). Only after a component in the new internal frame requests focus, the keyboard focus is actually transferred.

[mgarin]

Can you show a small example?
To be exact - can you show how you open new JInternalFrame?

And one more question - you are testing on Open JDK 7, right? There are many Swing issues on Open JDK as i know, so some components might behave incorrectly and should be modified to work properly.

[Sciss]

I tried to create a small example, but it doesn't exhibit this particular behaviour. So I'll have to dig deeper...

[mgarin]

That is why i asked for a small example :)
I didn't notice such behavior anywhere in my apps so far.

It is possible that something pulls focus back when new frame is opened.

[mgarin]

Any news?
Did you find the cause of this issue?

[Sciss]

Ok, so I think the issue is when the minimize etc. flags are activated, then when a new JInternalFrame is opened, the minimize button has initial focus. Below is an example that shows this behaviour. When the second frame is opened, pressing space bar activates the minimize button. At least here I have a visual feedback, in my original setup the button didn't get "depressed", so it was more unclear what happened.

I am not sure that minimize/maximize should actually be focusable or participate in the keyboard focus cycle. In any case, there is no indication that these widgets do have the focus (no focus ring or such is painted).

I think that even if you stick to these widgets being focusable, they should not have initial focus in the new window (which seems to be the case).

Best, .h.h.

(This is Scala code but it translates 1:1 to Java)

    package testing

    import javax.swing.{JPanel, JMenuItem, JMenu, JMenuBar, JDesktopPane, JLabel, AbstractAction, JButton, JInternalFrame, JFrame, UIManager}
    import com.alee.laf.WebLookAndFeel
    import java.awt.{BorderLayout, GraphicsEnvironment, EventQueue}
    import java.awt.event.ActionEvent

    object KeyboardTest extends App with Runnable {
      EventQueue.invokeLater(this)

      def run(): Unit = {
        WebLookAndFeel.install()

        val f = new JFrame()
        f.setBounds(GraphicsEnvironment.getLocalGraphicsEnvironment.getMaximumWindowBounds)
        val desk = new JDesktopPane
        f.setContentPane(desk)
        f.setVisible(true)

        val if1 = new JInternalFrame(null, true, true, true, true)
        val but = new JButton(new AbstractAction("Foo") {
          def actionPerformed(e: ActionEvent): Unit = {
            println("Aqui")
            val if2 = new JInternalFrame(null, true, true, true, true)
            desk.add(if2)

            val p = new JPanel {
              add(new JLabel ("Baz"), BorderLayout.NORTH)
              add(new JButton("Baz"), BorderLayout.SOUTH)
            }

            if2.getContentPane.add(p)
            if2.pack()
            if2.setLocation(200, 300)

            if2.setVisible(true)
            if2.toFront()
          }
        })
        desk.add(if1)

        if1.getContentPane.add(but)
        if1.pack()
        if1.setVisible(true)
        if1.toFront()
      }
    }

[mgarin]

Indeed, it seems that focusable buttons cause this issue.
I will simply make them non-focusable with the next update and the issue should be fixed.

[mgarin]

Should be fixed now with v1.27 update.
I also strongly recommend reading notes about StyleManager before updating.