Dir11 is loosing keyboard focus!

I have a kiosk application running WITHOUT a mouse. All
inputs is from the keyboard. The app is autostarting when Windows
starts.
After playing a Flash animation and a mpeg2 video (Mpeg adv
xtra) the application looses keyboard focus, wich result in Windows
warning sound when you press a key and the key is not sent to the
application.
The problem is solved if you click with a mouse, but there is
no mouse as I mentioned. The problem is NOT solved by <alt>
<tab>-switching forth and back.
I know this is an old MX2004 bug, and the work around then
was to set the document type to "tool". But this is not helping in
Dir11.
Anyone hwo has a work around?
Where to report bugs now a days? Does Adobe care at all?
(It's not easy to even find the Director support pages!)

Hi,
maybe you can use one of the Xtras than can simulate a
mouseclick?
Richard
"stageit ab" <[email protected]> wrote in
message
news:ganvvs$2as$[email protected]..
>I have a kiosk application running WITHOUT a mouse. All
inputs is
>from the
> keyboard. The app is autostarting when Windows starts.
> After playing a Flash animation and a mpeg2 video (Mpeg
adv xtra)
> the
> application looses keyboard focus, wich result in
Windows warning
> sound when
> you press a key and the key is not sent to the
application.
> The problem is solved if you click with a mouse, but
there is no
> mouse as I
> mentioned. The problem is NOT solved by <alt>
<tab>-switching forth
> and back.
>
> I know this is an old MX2004 bug, and the work around
then was to
> set the
> document type to "tool". But this is not helping in
Dir11.
>
> Anyone hwo has a work around?
> Where to report bugs now a days? Does Adobe care at all?
(It's not
> easy to
> even find the Director support pages!)
>
>
>

Similar Messages

How to detect loss of keyboard focus?

I’ve got a numeric input field that must be padded with
leading zeros to exactly 8 digits. The handler to pad the input is
trivial and calling the handler on various mouse events is equally
simple, however, I would also like to call the handler when the
input field looses keyboard focus by tabbing. Apparently, keyDown
events are not passed for the tab key when auto tabbing is engaged.
Anyone know if there is an event triggered by loss of focus?

There is no onBlur event in Lingo (though something like it
would be a
useful addition). You'll need to poll for keyboard focus.

On our project site, with Firefox 4 and 5, buttons don't take the keyboard focus if you mouse-click on them. Is this a problem of our site?

On a page like http://www.ori.uzh.ch/links.html, clicking a link opens a new tab, and after closing that tab, you can move to the next link with the tabulator key. On that site, it still works with Firefox 5. I also worked on our project site (password secured, sorry) with Firefox up to 3.6.18. But now, if I open a link with the mouse, close that tab again and press the tab key, the focus just goes to the first clickable button, as if I had not clicked any button previously. If I open a link by tab key and "enter", the keyboard focus is preserved on that button. But there are many many buttons on our pages, and they reload frequently.
BTW I adjusted the system preferences, so that the keyboard focus moves between all controls. (see http://www.tipstrs.com/tip/1505/Tab-key-to-select-form-elements-in-Firefox-on-the-Mac). But I don't think the problem is related to that.

I found out that our buttons are no links, but input tags, type="submit". I'll discuss the problem with our programmer.

Bug Report: The keyboard focus doesn't automatical...

Bug Report: When a conversation window opens, the focus doesn't automatically land in the chat entry text field.
Since the new interface for Skype was introduced officially in Skype 7.0, there is a bug with the system/keyboard focus for a new conversation window. When Skype is in "Split Window View" and each new conversation automatically pops up in a separate window, the system/keyboard focus doesn't land in the chat entry edit field. Instead, the user has to press Shift+TAB a couple of times, to move it there and reply to the chat message received. This especially problematic for screen reader users, who rely on keyboard navigation. This mainly occurs when a new conversation is started with an incoming message, but it sometimes occurs when moving the focus out of that conversation window and later back in it again (while it is still opened).
Steps to reproduce it:
1. From "View" menu, activate the "Split Window View", if it is not already enabled.
2. From Tools -> Options -> IM & SMS -> IM settings, enable "Open a new window when I receive a new message in Split Window View", if it is not already enabled.
3. From Tools -> Options -> Advanced, activate "Enable accessible mode", if it is not already enabled.
4. Activate the "Save" button, to save the changes.
5. Close all windows, related to Skype. You may keep only the main window opened.
6. Tell someone to send you a chat message. When the message arrives, Move the system focus to the conversation window in question, preferably with Alt+TAB. The system/keyboard will not land in the chat entry edit field as it did in Skype 6.21 and earlier and as it should by default, but in some unknown place in the window.
7. Move the system/keyboard focus in the chat entry edit field and keep it there.
8. Switch to another window, preferably from another application.
9. With Alt+TAB, switch back to the window of the opened Skype conversation. There is a chance that the system/keyboard focus will not land in the chat entry edit field as it did in Skype 6.21 and earlier and as it should do by default, but again in some unknown place in the conversation window. But that is harder to reproduce.
Test environment:
- Operating system: Windows 8.1 Pro N, 64-bit, in Bulgarian with all locale settings set to "Bulgarian".
- Skype version: 7.0.0.102 for Desktop.

This is a known problem, but Skype have not given us an estimated time for a fix.
Traditionally, Skype updates have been roughly monthly, so we are due a new version sometime soon. Many of us here are hoping that is has a bunch of fixes for the UI, the focus problem being one of them.
Sean Ellis - uses Skype chat for serious work
Click here to read my blog post on Skype 7 and basic principles of GUI design

Loss of keyboard focus in Java appl running under linux

I have a small sample program that replicates my problem. When this program is run a window is created. If you select File->New another instance of the program window is created. Now if you try to go back and bring to front the first window, keyboard focus is not
transferred when run under linux. You can only type in the second window. The expected behavior does happen in Windows.
> uname -a
Linux watson 2.6.20-1.2933.fc6 #1 SMP Mon Mar 19 11:38:26 EDT 2007 i686 i686 i386 GNU/Linux
java -versionjava version "1.5.0_11"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03)
Java HotSpot(TM) Client VM (build 1.5.0_11-b03, mixed mode, sharing)
javac -versionjavac 1.5.0_11
import java.awt.event.*;
import javax.swing.*;
class SwingWindow extends JFrame {
    SwingWindow() {
     super("SwingWindow");
     JMenuBar menuBar = new JMenuBar();
        JMenu fileMenu = new JMenu("File");
        JMenuItem newItem = new JMenuItem("New");
        newItem.addActionListener(new ActionListener() {
            public void actionPerformed(ActionEvent event) {
          SwingWindow.createAndShowGUI();
     fileMenu.add(newItem);
        menuBar.add(fileMenu);
        setJMenuBar(menuBar);
        setDefaultCloseOperation(JFrame.DISPOSE_ON_CLOSE);
     JTextField text = new JTextField(200);
     getContentPane().add(text);
     pack();
     setSize(700, 275);
    public static void createAndShowGUI() {
        JFrame frame = new SwingWindow();
        frame.setVisible(true);
    public static void main(String[] args) {
        javax.swing.SwingUtilities.invokeLater(new Runnable() {
            public void run() {
                createAndShowGUI();
}

You can implement the FocusListener interface. When
the first JFrame gains focus, call
text.requestFocusInWindow(). I hope this helps.The call requestFocusInWindow is not helping, perhaps even making it worse.
The problem seems to be that I am in the situation where the call
KeyboardFocusManager.getCurrentKeyboardFocusManager().getPermanentFocusOwner()
is returning the expected Component. The problem is that the KeyListener class that is registered with the Component is not being called when a key is being pressed.
The issue is that I have a component that has the keyboard focus, but the KeyListener class
is not responding.
This seems to be a linux only problem which makes it only mysterious.

JPanel loses keyboard focus

Ok, i have a JTextField which is initially disabled. A JPanel draws some stuff and receives keyboard input. When i enable the textfield, type some stuff, then press Esc (which disables it), i cant get the keyboard focus back on the JPanel. Here is an example:
(you can move the red circle before you enable the textfield, after you disable it, you cant move it anymore).
import java.awt.*;
import java.awt.event.*;
import javax.swing.*;
import javax.swing.border.*;
import javax.swing.event.*;
import java.util.Vector;
public class example extends JPanel implements ActionListener,Runnable {
    JFrame frame;
    JMenuBar menubar;
    JMenu m_file;
    JMenuItem mi_open,mi_close;
    JPanel canvas,northpanel;
    JTextField textfield;
    Image canvasimg;
    Thread thread=new Thread(this);
    private Image dbImage;     // for flickering
     private Graphics dbg;     // for flickering
     int x1=400,y1=200;
    public example() {
        frame = new JFrame("Example");                         // window
        frame.setLayout(null);
        frame.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
        frame.setPreferredSize(new Dimension(1000,700));
        frame.setLayout(new BorderLayout());
        northpanel=new JPanel();
        northpanel.setLayout(null);
        northpanel.setPreferredSize(new Dimension(1000,20));     northpanel.setLocation(0,0);
        menubar=new JMenuBar();
        m_file=new JMenu("File");
        mi_open=new JMenuItem("Open");
        mi_close=new JMenuItem("Close");
        m_file.add(mi_open);
        m_file.add(mi_close);
        m_file.getPopupMenu().setLightWeightPopupEnabled(false);
        menubar.add(m_file);
        northpanel.add(menubar);
        menubar.setLocation(0,0);     menubar.setSize(80,20);
        textfield=new JTextField();
        northpanel.add(textfield);
        textfield.setSize(200,20);     textfield.setLocation(500,0);
        textfield.setEnabled(false);
        frame.add(northpanel,BorderLayout.NORTH);
        canvas=new JPanel();
        canvas.setLayout(null);
        canvas.setSize(1000,600);
        canvas.setBackground(Color.white);
         frame.add(canvas,BorderLayout.CENTER);
        frame.pack();
        frame.setVisible(true);
        thread.start();                                   // start the thread
        textfield.addMouseListener(new MouseAdapter(){
                public void mousePressed(MouseEvent e){
                     textfield.setEnabled(true);
           textfield.addKeyListener(new KeyAdapter() {
             public void keyPressed(KeyEvent e){
                  int key=e.getKeyCode();
                  if(key==27){     // esc
                       textfield.setEnabled(false);
                       canvas.setEnabled(true);                // not working
                       canvas.requestFocus();
                       canvas.requestFocusInWindow();
           frame.addKeyListener(new KeyAdapter() {
             public void keyPressed(KeyEvent e){
                  int key=e.getKeyCode();
                  if(key==37){ //left
                       x1-=5;
                  if(key==38){ //up
                       y1-=5;
                  if(key==39){ //right
                       x1+=5;
                  if(key==40){ //down
                       y1+=5;
    // Create the GUI and show it.
    private static void createAndShowGUI() {
        JFrame.setDefaultLookAndFeelDecorated(true);
        example ex = new example();
    public void run(){
         while(true){
              try{
                   if(canvasimg==null)repaint();
                   Graphics g=canvas.getGraphics();
                   update(g);
                   thread.sleep(30);                                             // 1 sec
              }      catch(InterruptedException ex){}
    // ActionPerformed handles button and menu events
    public void actionPerformed(ActionEvent e){
    public static void main(String[] args) {
        //Schedule a job for the event-dispatching thread:
        //creating and showing this application's GUI.
        javax.swing.SwingUtilities.invokeLater(new Runnable() {
            public void run() {
                createAndShowGUI();
    public void update (Graphics g){          // get rid of flicker
          if (dbImage == null){
               dbImage = canvas.createImage (canvas.getSize().width, canvas.getSize().height);
               dbg = dbImage.getGraphics ();
          dbg.setColor (canvas.getBackground ());
          dbg.fillRect (0, 0, this.getSize().width, this.getSize().height);
          dbg.setColor (canvas.getForeground());
          paint (dbg);
          g.drawImage (dbImage, 0, 0, this);
     public void paint(Graphics g){
          g.drawImage(canvasimg,0,0,this);
          g.setColor(Color.red);
         g.fillOval(x1,y1,10,10);
    public void repaint(){
         if(canvas!=null && canvasimg==null)canvasimg=canvas.createImage(1000,670);
         if(canvasimg==null)return;
         Graphics g=canvasimg.getGraphics();
         if(g==null)return;
         g.setColor(Color.white);
         g.fillRect(0,0,1000,600);
}

OK great guru since you're so damn confident that you're doing everything right, find out for yourself why this works and yours doesn't.
I could list a few dozen things wrong with your code, but I'd be wasting my keystrokes.import java.awt.BorderLayout;
import java.awt.Color;
import java.awt.Dimension;
import java.awt.Graphics;
import java.awt.event.KeyAdapter;
import java.awt.event.KeyEvent;
import java.awt.event.MouseAdapter;
import java.awt.event.MouseEvent;
import javax.swing.JFrame;
import javax.swing.JMenu;
import javax.swing.JMenuBar;
import javax.swing.JMenuItem;
import javax.swing.JPanel;
import javax.swing.JTextField;
import javax.swing.SwingUtilities;
public class TextFieldDisableNoProblem extends JPanel {
   JPanel northPanel;
   JMenuBar menubar;
   JMenu m_file;
   JMenuItem mi_open,mi_close;
   JTextField textField;
   int x1 = 400;
   int y1 = 200;
   public TextFieldDisableNoProblem () {
      setBackground (Color.WHITE);
      addKeyListener (new KeyAdapter () {
         public void keyPressed (KeyEvent e){
            int key = e.getKeyCode ();
            switch (key) {
               case KeyEvent.VK_LEFT:
                     x1 -= 5;
                     break;
               case KeyEvent.VK_UP:
                     y1 -= 5;
                     break;
               case KeyEvent.VK_RIGHT:
                     x1 += 5;
                     break;
               case KeyEvent.VK_DOWN:
                     y1 += 5;
                     break;
            repaint ();
   void makeUI () {
      JFrame frame = new JFrame ("");
      frame.setDefaultCloseOperation (JFrame.EXIT_ON_CLOSE);
      frame.setSize (600, 500);
      frame.setLocationRelativeTo (null);
      menubar=new JMenuBar ();
      m_file=new JMenu ("File");
      mi_open=new JMenuItem ("Open");
      mi_close=new JMenuItem ("Close");
      m_file.add (mi_open);
      m_file.add (mi_close);
      menubar.add (m_file);
      frame.setJMenuBar (menubar);
      textField=new JTextField ();
      textField.setEnabled (false);
      textField.setBounds (200, 0, 200, 20);
      textField.addMouseListener (new MouseAdapter (){
         public void mousePressed (MouseEvent e){
            textField.setEnabled (true);
      textField.addKeyListener (new KeyAdapter () {
         public void keyPressed (KeyEvent e){
            int key = e.getKeyCode ();
            if(key == KeyEvent.VK_ESCAPE){
               textField.setEnabled (false);
               requestFocus ();
      northPanel=new JPanel ();
      northPanel.setLayout (null);
      northPanel.setPreferredSize (new Dimension (600,20));
      northPanel.add (textField);
      frame.add (northPanel,BorderLayout.NORTH);
      frame.add (this, BorderLayout.CENTER);
      frame.setVisible (true);
      requestFocus ();
   public void paintComponent (Graphics g) {
      super.paintComponent (g);
      g.setColor (Color.RED);
      g.fillOval (x1, y1, 10, 10);
   public static void main (String[] args) {
      SwingUtilities.invokeLater (new Runnable () {
         public void run () {
            JFrame.setDefaultLookAndFeelDecorated (true);
            new TextFieldDisableNoProblem ().makeUI ();
}db

JComboBox popup list remains open after losing keyboard focus

Hi,
I have noticed a strange JComboBox behavior. When you click on the drop down arrow to show the popup list, and then press the Tab key, the keyboard focus moves to the next focusable component, but the popup list remains visible.
I have included a program that demonstrates the behavior. Run the program, click the drop down arrow, then press the Tab key. The cursor will move into the JTextField but the combo box's popup list is still visible.
Does anyone know how I can change this???
Thanks for any help or ideas.
--Yeath
import java.awt.*;
import javax.swing.*;
import java.util.*;
public class Test extends JFrame
   public Test()
      super( "Test Application" );
      this.getContentPane().setLayout( new BorderLayout() );
      Box box = Box.createHorizontalBox();
      this.getContentPane().add( box, BorderLayout.CENTER );
      Vector<String> vector = new Vector<String>();
      vector.add( "Item" );
      vector.add( "Another Item" );
      vector.add( "Yet Another Item" );
      JComboBox jcb = new JComboBox( vector );
      jcb.setEditable( true );
      JTextField jtf = new JTextField( 10 );
      box.add( jcb );
      box.add( jtf );
   public static void main( String[] args )
      Test test = new Test();
      test.pack();
      test.setVisible( true );
      test.setDefaultCloseOperation( JFrame.EXIT_ON_CLOSE );
}

ran your code on 1.5.0_3, observed problem as stated.
even though the cursor is merrily blinking in the textfield, you have to click into
the textfield to dispose the dropdown
ran your code on 1.4.2_08, no problems at all - tabbing into textfield immediately
disposed the dropdown
another example of 'usual' behaviour (involving focus) breaking between 1.4 and 1.5
the problem is that any workaround now, may itself be broken in future versions

My MacBook Pro Retina's Bluetooth chipset unknown/odd login message on the login screen states Login Window Authentication Login window Name edit text has keyboard focus. In addition, the login screen is not remembering me

I have been experiencing several issues with my MacBook Pro Retina mid 2012. My MBPR is scheduled to go into the depot. However, I am wondering if anyone may be able to shed light on a few issues as this is the third "official" time my MBPR is going back for service ("one depot" trip; "one authorized" dealer; several in-store visits).
My Bluetooth is stating that the Bluetooth Chipset is Unknown (0). I also have had Bluetooth Preferences mysteriously change on me. In addition, while Bluetooth is off there are two serial modems turning on. I have turned them off, but they continue to pop up.
In addition, when I log in, my MBPR is not remembering me and my login name is not appearing on the slate-gray screen. The name and password are blank and the following message appears in the lower left hand corner. "login window authentication login window Name edit text has keyboard focus." As a side note, I am the only user. The login issue is a recent occurrence as we just totally wiped it again via a Command + R, and I don't believe I have an accessibility setting set to anything that would cause this, but wanted to check.
Should I be concerned here? Has anyone else had issues like this? I don't want to worry if I don't have to. I have had so many issues over the course of nine months. 5-6 wipes. Airport card replaced and I am about to pull my hair out if my MBPR doesn't come back worldly like clock work this time. I just can't send my days trying to get a $2300 product to work for me any longer. No idea what is wrong with it, but it is driving me insane. Cross your fingers for me and any guidance you have or thoughts would be welcomed. Thank you. EMM

A few more issues...
In Console, the following is greyed out:
User and Diagnostic reports
Com.apple.launchd.peruser.0
Com.apple.launchd.peruser.88
Com.apple.launchd.peruser.89
Com.apple.launchd.peruser.92
Com.apple.launchd.peruser.97
Com.apple.launchd.peruser.200
Com.apple.launchd.peruser.201
Com.apple.launchd.peruser.202
Com.apple.launchd.peruser.212
*[user logs are accessible]
Krb5kdc
Radius
My guest files are locked, but again I am the administrator of MBPR.
I am worried about a keystroke logged or at least, trying to rule it out.
Also:
Mdworker32(225) [and other mdworker numbers] are sandboxing; stating deny Mach-lookup
Com.apple.Powermanagement.control, etc. long attachment with those files with version: ??? (???).
Postinstall: removing applications/Microsoft Office 2011/Microsoft Outlook.app
WARNINGS in Console include:
[NSImage compositeToPoint:fromRect:operation:fraction:] is deprecated in MacOSX 19.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction] instead.
There are a ton of other warnings. Before I go through this again, can someone tell me if this is normal (all of it -- above too); or if these are symptoms is a keystroke logger or hardware issues?
I ask because originally, when my computer went in for diagnostics (more than once), Apple stated the hardware was fine (other than Airport Card -- finally). However, if I've done 5-6 total wipes; created new users; do not have sharing set-up; have not played around in Terminal; and am up-to-date with versions -- and various issues KEEP COMING BACK -- I am left wondering if a keystroke logger would be possible here?!? I thought maybe a faulty logic board, but why would diagnostics be okay, then? Not trying to be hyperbole, just desperate.
Please help me rule keystroke logger out or at least, tell me so I know, so I can take appropriate action. If you think it could be the logic board with symptoms above, that would be a great too.
All I want to do is use the computer as intended, but I can't seem to get a real answer, so after nine months -- I am turning to the communities to see if anyone -- anyone at all -- can help. The last thing I can do is have the MBPR come back from the depot and the same thing occur. Any guidance or advice would be so gratefully appreciated.

Calling1.4.1 signed applet from Javascript causes keyboard/focus problems

Pretty sure there's a JRE bug here, but I'm posting to forums before I open one in case I'm missing something obvious :-)
This issue may be specific to IE, I haven't tested elsewhere yet. Our web application is centered around a signed applet that is initialized with XML data via Javascript. We first noticed the problem when our users started upgrading from the 1.3.x plug-in to the 1.4.x plug-in. The major symptom was that shortcut keys stopped working. I debugged the problem off and on for about a month before I boiled it down to a very simple program that demonstrates the issue (included below). Basically, the program has a function that adds a JButton to a JPanel and registers a keyboard listener (using the new DefaultKeyboardFocusManager class) that prints a message to the console. This function is called by the applet's init() method, as well as by a public method that can be called from Javascript (called callMeFromJavascript()). I also included a very simple HTML file that provides a button that calls the callMeFromJavascript() method. You can test this out yourself: To recreate, compile the class below, JAR it up, sign the JAR, and put in the same dir with the HTML file. Load the HTML file in IE 5.0 or greater, and bring the console up in a window right next to it. Now click the button that says init--you should see the small box appear inside the button that indicates it has the focus. Now press some keys on your keyboard. You should see "KEY PRESSED!!!" appearing in the console. This is proper behavior. Now click the Init Applet from Javascript button. It has removed the button called init, and added one called "javascript". Press this button. Notice there is no focus occurring. Now press your keyboard. No keyboard events are registered.
Where is gets interesting is that if you go back and make this an unsigned applet, and try it again, everything works fine. This bug only occurs if the applet is signed.
Furthermore, if you try it in 1.3, signed or unsigned, it also works. So this is almost certainly a 1.4 bug.
Anyone disagree? Better yet, anyone have a workaround? I've tried everything I could think of, including launching a thread from the init() method that sets up the components, and then just waits for the data to be set by Javascript. But it seems that ANY communication between the method called by Javascript and the code originating in init() corrupts something and we don't get keyboard events. This bug is killing my users who are very reliant on their shortcut keys for productivity, and we have a somewhat unique user interface that relies on Javascript for initialization. Any help or suggestions are appreciated.
================================================================
Java Applet (Put it in a signed JAR called mainapplet.jar)
================================================================
import javax.swing.*;
import java.awt.*;
import java.awt.event.*;
public class MainApplet extends JApplet implements KeyEventDispatcher
    JPanel test;
    public void init()
        System.out.println("init called");
        setUp("init");
    public void callMeFromJavascript()
        System.out.println("callMeFromJavascript called");
        setUp("javascript");
    private void setUp(String label)
        getContentPane().removeAll();
        test = new JPanel();
        getContentPane().add( test );
        JButton button = new JButton(label);
        test.add( button );
        test.updateUI();
        DefaultKeyboardFocusManager.getCurrentKeyboardFocusManager().addKeyEventDispatcher(this);
    public boolean dispatchKeyEvent(KeyEvent e)
        System.out.println("== KEY PRESSED!!! ==");
        return false;
}================================================================
HTML
================================================================
<form>
<APPLET code="MainApplet" archive="mainapplet.jar" align="baseline" id="blah"
     width="200" height="400">
     No Java 2 SDK, Standard Edition v 1.4.1 support for APPLET!!
</APPLET>
<p>
<input type="button" onClick="document.blah.callMeFromJavascript();" value="Init Applet via Javascript">
</form>

I tried adding the requestFocus() line you suggested... Same behavior.
A good thought, but as I mention in my description, the applet has no trouble gaining the focus initially (when init() is called). From what I have seen, it is only when the call stack has been touched by Javascript that I see problems. This is strange though: Your post gave me the idea of popping the whole panel into a JFrame... I tried it, and the keyboard/focus problem went away! It seems to happen only when the component hierarchy is descended from the JApplet's content pane. So that adds yet another variable: JRE 1.4 + Signed + Javascript + components descended from JApplet content pane.
And yes, signed or unsigned DOES seem to make a difference. Don't ask me to explain why, but I have run this little applet through quite a few single variable tests (change one variable and see what happens). The same JAR that can't receive keyboard events when signed, works just fine unsigned. Trust me, I'm just as baffled as you are.

Outlook window getting the keyboard focus instead of user created Form Window during Outlook Startup

This MAPILogonComplete method involves creating a Form Window to show "What's New" of a certain Addin version (DisplayWhatsNewDialog() in the code):
private void _outlook_MAPILogonComplete() {
_logger.Info("_outlook_MAPILogonComplete");
try
if (_timerForm != null)
_timerForm.Timer.Stop();
_timerForm.Timer.Dispose();
catch (Exception ex2)
_logger.Error(ex2.Message, ex2);
try
if (Globals.BJNSettings.showWhatsNew)
Globals.BJNSettings.showWhatsNew = false;
UIHelper.DisplayWhatsNewDialog(false);
Ol.Inspector insp = null;
if (_inspectors.Count > 0)
for (int i = _inspectors.Count; i >= 1; i--)
insp = _inspectors[i];
WrapInspector(insp);
insp = null;
Ol.Explorer expl = null;
if (_explorers.Count > 0)
for (int i = _explorers.Count; i >= 1; i--)
expl = _explorers[i];
WrapExplorer(expl);
expl = null;
GetAddinsList();
Thread logSystemInfoThread = new Thread(new ThreadStart(LogSystemInformation));
logSystemInfoThread.TrySetApartmentState(ApartmentState.STA);
logSystemInfoThread.IsBackground = true;
logSystemInfoThread.Start();
try
Ol.NameSpace ns = _outlook.GetNamespace("MAPI");
_calFolder = ns.GetDefaultFolder(Ol.OlDefaultFolders.olFolderCalendar) as Ol.Folder;
_calFolder.BeforeItemMove += new Ol.MAPIFolderEvents_12_BeforeItemMoveEventHandler(_calFolder_BeforeItemMove);
_delFolder = ns.GetDefaultFolder(Ol.OlDefaultFolders.olFolderDeletedItems) as Ol.Folder;
Marshal.ReleaseComObject(ns);
ns = null;
catch (Exception ex)
_logger.Error(ex.Message, ex);
UIHelper.WriteDoNotDisableKeyToRegistry();
Globals.AppointmentsToProcess = new List<string>();
_timerForm.ProcessTimer.Interval = 3000;
_timerForm.ProcessTimer.Start();
catch (Exception ex)
_logger.Error(ex.Message, ex);
DisplayWhatsNewDialog() has this signature:
public static void DisplayWhatsNewDialog(bool modal)
try
string defaultWhatsNewFile = Globals.BJN_APP_BASE_DIRECTORY + "WhatsNew.txt";
string localISOLanguageName = Languages.GetTwoLetterISOLanguageName();
string localizedWhatsNewFile = Languages.GetInstalledLocalizedFilePath(localISOLanguageName, "WhatsNew.txt");
if (String.IsNullOrEmpty(localizedWhatsNewFile))
localizedWhatsNewFile = defaultWhatsNewFile;
if (File.Exists(localizedWhatsNewFile))
BJNWhatsNew whatsNew = new BJNWhatsNew(localizedWhatsNewFile);
if (modal)
whatsNew.ShowDialog();
whatsNew.Dispose();
else
whatsNew.TopMost = true;
whatsNew.Show();
whatsNew = null;
catch (Exception ex)
_logger.Error(ex.Message, ex);
The problem is if the Window is made modal, it blocks the Outlook to launch and also goes back of the Outlook loading window (Whats New window will not be having keyboard focus). And if the Window is made non-modal (passing false to DisplayWhatsNewDialog()),
Outlook launches properly and What's New window comes at the top but will not be having keyboard focus; instead the launched Outlook window will be having the keyboard focus. May anyone please suggest a way to make the What's New window to be always having
the keyboard focus? Structure of form window class BJNWhatsNew is given below:
public partial class BJNWhatsNew : Form
private static ILog _logger = LogManager.GetLogger(typeof(BJNWhatsNew));
public BJNWhatsNew(string whatsNewTextFileName)
InitializeComponent();
InitLabels();
InitEventHandlers();
InitWhatsNew(whatsNewTextFileName);
private void InitLabels()
try
this.Text = Properties.Resources.bjn_version_info_caption;
this.buttonClose.Text = Properties.Resources.ok_hotkey;
this.labelBJNAddin.Text = Properties.Resources.bjn_version_ol_addin;
this.labelVersion.Text = String.Format(Properties.Resources.version_format, Assembly.GetExecutingAssembly().GetName().Version.ToString(3));
Assembly assembly = Assembly.GetExecutingAssembly();
FileInfo fileInfo = new FileInfo(assembly.Location);
DateTime buildDate = fileInfo.LastWriteTime;
string formatString = "d MMM, yyyy";
this.labelReleaseDate.Text = String.Format(Properties.Resources.bjn_version_release_date, buildDate.ToString(formatString));
catch (Exception ex)
_logger.Error(ex.Message, ex);
private void InitEventHandlers()
this.buttonClose.Click += new EventHandler(buttonClose_Click);
private void InitWhatsNew(string whatsNewTextFileName)
try
if (File.Exists(whatsNewTextFileName))
StreamReader sr = new StreamReader(whatsNewTextFileName);
string whatsNew = sr.ReadToEnd();
sr.Close();
this.richTextBox1.Text = whatsNew;
this.richTextBox1.SelectionLength = 0;
this.buttonClose.Select();
this.buttonClose.Focus();
catch (Exception ex)
_logger.Error(ex.Message, ex);
void buttonClose_Click(object sender, EventArgs e)
this.Close();

Hello Prasad,
The ShowDialog method will block the current thread. If you want to continue working with Outlook objects you need to use the Show method instead. The key fact is that both methods (Show and ShowDialog) accepts an instance of the IWin32Window interface
which allows to specify the parent window handle. Specifying the parent window handle (Outlook Explorer window) to the Show method you can make your window shown on top of Outlook all the time.
To get the HWND of an Outlook explorer object (e.g. Application.ActiveExplorer), cast it to IOleWindow and call IOleWindow.GetWindow(). Also you may find the
How to get the IWin32Window for Outlook
article helpful.

Applet looses its focus in IE

Hello, all!
I working with applet that will be used as a simple code editor with highlighting of different programming languages.
This applet based on JTextPane wrapped in JScroll pane. When I test this applet with java applet viewer - all works fine, but now I embedded my applet into html page and try to test it in "live" conditions using IE browser.
When I press TAB key inside of JTextPane the appled looses its focus instead of simply insert an indent as it should be.
Interesting, that this problem reproduces only under IE (in Firefox it works properly).
Maybe someone knows how to workaround this problem?
I'll be very thankfull for answers!
With best regards,
Andrew.

Thanks for all who participated in resolving of my problem. It's eventually has been resolved by myself.
The solution was very complicated and looks like unskilful workaround, but it was one, which really helped.
So now I just want to describe it, maybe someone else will faced the similar problem.
First I added to main class of applet following public method (for manual handling of tab key):
public void handleTab() throws Exception{
     textPane.grabFocus();
     Document doc = textPane.getDocument();
     doc.insertString(textPane.getCaretPosition(), "\t", null);
     textPane.setCaretPosition(textPane.getCaretPosition() + 1);
}After that I simply can invoke this method from JScript. So my wrapping page can be like this:
<HTML>
<HEAD>
<BODY>
<APPLET CODEBASE="." ARCHIVE="editor.jar" CODE="editor.applet.EditorApplet.class" NAME="editor" WIDTH="640" HEIGHT="480" MAYSCRIPT >
</APPLET>
<INPUT name="stub1" type=text onfocus="editor.handleTab();" style="position:absolute; top:100; left:100;">
<INPUT name="stub2" type=text onfocus="stub1.focus();" style="position:absolute; top:150; left:100;">
</BODY>
</HTML>I know, this looks little bit strange, so let me clearify some details and aspects of IE behavior.
- When I press TAB, focus goes to "stub1" input box, which invokes 'editor.handleTab' immediately. But inspite of focus was grabbeg back by applet (invoking textPane.grabFocus()), it is ALSO REMAIS IN BROWSER in inputbox. So when I press TAB again, focus moves not to "stub1" again, but to the next flow control "stub2". So in this case "stub2" must return the focus to "stub1". It is like chain reaction ;-)
- both input box stubs has an absolute positioning and simply hidden under the applet, so all these manipulations are invisible for end-user of applet and looks like 100%-natural behavior of any editable text area.

Switching windows in Linux/Firefox loses keyboard focus. Workarounds?

Hi,
I've been stumbling on an issue in which an applet gets into a state where it can receive mouse events but not keyboard events. This state occurs some of the time when switching from a non-modal dialog to the applet.
I've witnessed this behavior on:
Linux (fc8), Firefox 3.0.10, Java plug-in 1.6.0_13, Gnome 2.20.3
Sun Solaris (5.10), Firefox 3.0.8, Java plug-in 1.6.0_12, Sun Java Desktop System or CDE
I can not reproduce this behavior using appletviewer, nor can I reproduce it on the Mac (Opera/Firefox/Safari), nor on Windows (Firefox/IE).
I've crafted some code that shows the behavior:
FocusApplet.java:
import javax.swing.JApplet;
import java.awt.*;
import java.awt.event.*;
import javax.swing.*;
import javax.swing.border.*;
import javax.swing.event.*;
import java.beans.*;
public class FocusApplet extends JApplet {
JTextArea infoText;
    Object activeWindow;
    Object focusOwner;
    Object permanentFocusOwner;
       Applet contains two components.
       NORTH: Text field
       CENTER: Info text
       The info text is updated whenever the following
       KeyboardFocusManager properties change:
          activeWindow
       focusOwner
       permanentFocusOwner
public void init(){
      JTextField tf = new JTextField("Type here");
      infoText = new JTextArea();
      infoText.setEditable(false);
      infoText.setLineWrap(true);
      infoText.setWrapStyleWord(true);
      infoText.setBorder(new EtchedBorder());
      this.add(infoText, BorderLayout.CENTER);
      this.add(tf, BorderLayout.NORTH);
      KeyboardFocusManager focusManager =
       KeyboardFocusManager.getCurrentKeyboardFocusManager();
      activeWindow=focusManager.getActiveWindow();
      permanentFocusOwner=focusManager.getPermanentFocusOwner() ;
      focusOwner=focusManager.getFocusOwner() ;
      updateText();
      focusManager.addPropertyChangeListener(
       new PropertyChangeListener() {
         public void propertyChange(PropertyChangeEvent e) {
          String prop = e.getPropertyName();
          if ("focusOwner".equals(prop)) {
              focusOwner = e.getNewValue();
              updateText();
          } else if ("permanentFocusOwner".equals(prop)) {
              permanentFocusOwner = e.getNewValue();
              updateText();
          } else if ("activeWindow".equals(prop)) {
              activeWindow = e.getNewValue();
              updateText();
      // Create non-modal dialog
      JDialog jdl = new JDialog((Frame)null,"Extra dialog",
                    false/*modal*/);
      jdl.setSize (300,550);
      jdl.setVisible(true);
    public void updateText() {
     infoText.setText("Active window: "+getName(activeWindow)+
        "\nFocus owner: "+getName(focusOwner)+
        "\nPermanent focus owner: "+getName(permanentFocusOwner));
    public String getName(Object obj) {
     return (obj==null) ? "null" : obj.getClass().getName();
}Applet HTML:
<applet code="FocusApplet.class" width="400" height="400"></applet>When I run this applet, I can click on the text field ("Type here") and enter text. Then, I switch between the empty dialog box and the applet using the window manager. (I.e., clicking on the dialog, then clicking on the applet.) Sometimes I see the following Keyboard Focus settings when I bring the applet to the front:
Active window: sun.plugin.viewer.frame.XNetscapeEmbeddedFrame
Focus owner: javax.swing.JTextField
Permanent focus owner: javax.swing.JTextField
In this case, clicking on the text field will allows the user to edit text. Good! However, 10%-50% of the time I get the following settings after I bring the applet to the front:
Active window: null
Focus owner: null
Permanent focus owner: javax.swing.JTextField
In this case, I can click on the applet, and I can highlight text in the text field, but I can not edit the text. (No carat appears. Bad!) Since there is no keyboard focus owner, the applet appears non-responsive.
I have a few questions:
1. Is this a Java plug-in bug? A Firefox bug? Who do I file a bug with, assuming there's not something I'm missing?
2. Can anyone suggest a workaround?
Thanks,
-David-

I noticed the problem too. Is there any fix or workaround? Friends using Windows say that all is ok.
Linux x86_64 (Gentoo), Firefox 3.5.1, jre 1.6.0.15.

508 accessibility and keyboard focus

I'm using Captivate 4 and can't seem to get the keyboard accessibility to work properly. I want to be able to control the tab order and keyboard focus on each slide. For example, if the user keeps pressing tab they will eventually move from the .swf file and begin reading the address and menu bar in the browser window. Does anyone know how to ensure that the keyboard focus is provided only to active elements?

Hi,
I noticed your post while searching for the same answer with respect to Captivate 5. So far, it is the closest I've seen to the problem I'm trying to resolve. I see that you had no luck here, but was wondering if you found a solution elsewhere. All help would be appreciated.

Safari keyboard focus after a search

I like using the keyboard as often as I can. With Chrome, I can hit the Tab key after searching from the search/URL bar. This moves the keyboard focus to the web page, which causes an arrow to appear in front of the first search result. With up/down keys and Enter, you can then go to any of the search results.
What is the proper hotkey in Safari to move the keyboard focus from the search bar to the webpage?
(Using Safari 7 on OS X)

I think I found out why this didn't work -- in System Preferences -> Keyboard -> Shortcuts, I've got the "Full Keyboard Access" option set to "All Controls"...

JTextArea doesn't loose the focus

Hi everybody,
I programmed a graphical interface with two JTextAreas and six JTextFields. Using the program
means that I delete the text of both JTextAreas and paste new text. An algorithm calculates
the results. After that I insert new text and start the algorithm again. After two or three deletions
and insertions one of the JTextAreas doesn't loose the focus and I can't write on it, but I can
click to another field or area and then I have got two mouse pointer.
I hope someone has an idea.
Thank you for your help. Katja

Please post your code so that somebody may check for
you.Here the source code of one JTextArea.
seq1label = new JLabel("Target sequence:");
     sequence1 = new JTextArea("MAEPFSTILGTDGSGGRCKYLNKGIVGLGSYG", 10, 100);
     sequence1.setFont(fontplain);
     sequence1.setBackground(general.BACKCOLOR);
     JScrollPane scrollpane1 = new JScrollPane(sequence1);
     JPanel panelseq1 = general.makePanel();
     panelseq1.setLayout(new BorderLayout());
     panelseq1.add(introduction, BorderLayout.NORTH);
     panelseq1.add(seq1label, BorderLayout.CENTER);
     panelseq1.add(scrollpane1, BorderLayout.SOUTH);
I hope it is enough.

Dir11 is loosing keyboard focus!

Similar Messages

Maybe you are looking for