Losing Focus to greedy dialog

I have a main JFrame and a JDialog to accompany it as a kind of toolbar. The user types in the main frame, and the dialog stays in the foreground of the frame at all times. It's a setup similar to MS Word with one of the toolbars (say the Font toolbar) floating - in which I need the main frame to keep focus so that the user can keep typing. The problem is, the dialog keeps wanting to steal the focus, so the user can't type.
I've tried all sorts of things, from telling the main frame to request the focus, the custom text area to grab the focus... I added a windowListener to the dialog so that whenever it gained the focus, the text area would grab the focus again. I even did a dialog.setFocusable(false); yet it still takes the focus.
When does it take the focus, you ask? Obviously it doesn't do it constantly - I have another dialog that pops up when the user clicks a button - an options dialog (modal), that when it completes, it destroys and creates a new accompanying dialog, and then after I tell it to set the dialog to visible, it steals the focus (even though it's not focusable). I tried immediately after setting it to visible, having the text area grab the focus again, but still to naught. I've almost resorted to using the swing thread to grab the focus every so often.
What do I do?

Swing related questions should be posted in the Swing forum.
The dialog will only take focus if you click on it. Otherwise focus will stay with the main frame. You can always make your buttons on the dialog non-focusable. You can also try:
Window.setFocusableWindowState(false);If you need further help then you need to create a [Short, Self Contained, Compilable and Executable, Example Program (SSCCE)|http://homepage1.nifty.com/algafield/sscce.html], that demonstrates the incorrect behaviour.
Don't forget to use the [Code Formatting Tags|http://forum.java.sun.com/help.jspa?sec=formatting], so the posted code retains its original formatting.

Similar Messages

  • Window losing focus

    Hi all,
    I was wondering if it were at all possible for a JFrame or JWindow to listen for an event when the window is about to lose focus - ie it is losing focus (as opposed to lost focus).
    WindowEvent and the subsequent WindowFocusListener interface only caters for handling a window having already lost or gained focus, however I need to make things happen before the window actually loses its focus.
    Can anyone help?
    Regards,
    Andrew.

    Hi Andrew,
    I don't know a possibility to get an event like you want to have - and I do think such an eevnt does not exist.
    But I do think you really wouldn't need such a possibility. Perhaps you can give a short explanation why you need this possibility. If the problem is to regain the focus there is a post from me a few minutes ago (I'm sorry about not knowing how to reference to other posts but I hope since years I will learn such things). If you have other problems please explain the problem - perhaps there is another way of solving it.
    HTH and greetings from
    Holger

  • Airport Losing Focus??

    I have a Mac set as an FTP server at a second location for backing up. My server at my first location will start backing up, completing some files. After a while, the network light on the modem at location 2 will stop blinking (indicating no traffic). The message from my backup software is "(FTP: server disconnected or timed out)". I can browse the web with no problems when this is happening. Is my Airport Extreme just losing focus?
    Also, pod casts will not down load to same FTP server. I'll get anywhere from 1/8 to 1/2 of a pod cast before the network traffic light stops blinking.
    Help! Boss is getting nervous. Thanks.

    Thanks JJMack.  I was hoping it wasn't the card I was using.  This is the first time I've used a geforce card on my work PC.  However it's not the first time I've used them with Adobe's apps.  For years my personal PCs had them and usually without issues like this.  We chose to attempt to use this new Geforce GTX980 card because of how much further advanced it is over midrange Quadro cards at the moment, and because of some of the other software I am using that is more viewport and video ram dependent.  Adobe applications are still my mainstay but we couldn't justify the purchase of older technology midrange K4000 cards that were supposedly newer than my older 4000.  As these still had older PCI connections than the HP workstations we built, among other tech such as cuda core amounts that are drastically behind the times.  Jumping up to 6000 level Quadro cards for up to date technology just isn't in the budget as the prices are astronomical. As with the Titan cards cards that are high priced and yet older tech.  So we made the decision to try the GTX card for a while.  Right now this sporadic window focus issue seems to be the only new issue I've run into so far.   I'm sure I will see more in the near future doing something if the card is the issue.  Maybe the new types of hardware being used such as the PCI express hard drive, or very recent photoshop updates can be blamed.  Just not figuring it out just yet.
    I was informed by an IT professional here that has application creation experience that this truly seemed like an application problem more than a graphic card problem.   But until someone can corroborate that thought I guess I'm going to keep blaming the newer GTX card or wait to see if an App update makes this go away quietly.  No one else has chimed in yet.  Thanks for the link.

  • Losing focus in file navigation dialogs

    I've been searching on here and Leopard seems to have a number of focus problems. I think I may have found another.
    Try this: under 10.5.2, launch iTunes and open any of its file navigation dialogs. Select any folder or file but don't click "Open." Now Command-Tab to the Finder or any other app. When you Command-Tab back to iTunes focus has been lost on the file dialog. This behaviour also occurs if you activate the screensaver.
    It also happens with these third-party applications: Graphic Converter 6.0.3, Final Draft 7.1.3, Final Draft Tagger 1.2.2, TextWrangler 2.3, Screenwriter 6.0.2.109 (r3).
    This does not happen with any of the following Apple applications: AppleScript, Automator, Font Book, GarageBand, iCal, iDVD, iMovie, iPhoto, iWeb, Keynote 4.0.2, Numbers 1.0.2, Pages 3.0.2, Mail, Preview, QuickTime Player, Safari, Stickies, TextEdit.
    It also does not happen with these third-party applications: Bean 0.9.11, Little Snitch Configuration 2.0.2, NotePad 2.6b1, Scrivener 1.11.
    Graphic Converter's developer maintains that these dialogs are handled by the Mac OS and he can do nothing to change this behaviour. If this is true, why the disparity in my test results?
    Kind regards.

    This is on a brand new iMac 24" 2.4 GHz Core Duo with the stock Radeon HD2600 graphics card. I reinstalled the system and bundled software to leave out unnecessary printer drivers and language translations, then applied the 10.5.2 Combo updater, followed by the Graphics Update. Problems with HelpViewer were resolved by trashing its cache and .plist files. I then installed my third-party apps.
    Graphic Converter was the first app to manifest the focus problem. I reported this to Lemkesoft Tech Support and was informed that this was a Mac OS issue so I decided to test all apps on this machine. As stated, iTunes is the only Apple application to exhibit this behaviour (although I have not yet tested the utilities).
    Kind regards.

  • Dialog title shows weird characters when losing focus

    Hi all,
    a localized application with two configured languages has problems with the title of a modal dialog. Opening the dialog works fine, the text is displayed properly. After klicking into the main screen (so the modal dialog loses the focus), some weird characters are displayed in the title (looks chinese). The buttons that are localized with the same resourcebundle stay normal. Does anybody know this problem?
    Regards, Robert4

    More information:
    This problem does not occur at all workstations. Some do not have this problem at all. But it's all on Windows XP SP 1.
    Maybe a threading problem? I cannot imagine.........
    regards, 'Robert4

  • JTable custom cell editor losing focus

    This is a followup to Re: Tutorial on AWT/Swing control flow wherein I ask for pointers to help me understand the source of focus-loss behaviour in my JTable's custom cell editor.
    I have done some more investigations and it turns out that the focus loss is a more general problem with custom cell editors which call other windows. Even the color-picker demo in the JTable tutorial at http://download.oracle.com/javase/tutorial/uiswing/examples/components/index.html#TableDialogEditDemo has this problem, IF you add a text field or two to the layout BEFORE the table. The only reason the table in the demo doesn't lose the focus when the color-picker comes out is because the table is the only thing in the window!
    Here is the demo code, augmented with two text fields, which are admittedly ugly here but which serve the desired purpose:
    * Copyright (c) 1995, 2008, Oracle and/or its affiliates. All rights reserved.
    * Redistribution and use in source and binary forms, with or without
    * modification, are permitted provided that the following conditions
    * are met:
    *   - Redistributions of source code must retain the above copyright
    *     notice, this list of conditions and the following disclaimer.
    *   - Redistributions in binary form must reproduce the above copyright
    *     notice, this list of conditions and the following disclaimer in the
    *     documentation and/or other materials provided with the distribution.
    *   - Neither the name of Oracle or the names of its
    *     contributors may be used to endorse or promote products derived
    *     from this software without specific prior written permission.
    * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS
    * IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
    * THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
    * PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE COPYRIGHT OWNER OR
    * CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
    * EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
    * PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
    * PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
    * LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
    * NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
    * SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
    import javax.swing.*;
    import javax.swing.border.Border;
    import javax.swing.table.AbstractTableModel;
    import javax.swing.table.TableCellEditor;
    import javax.swing.table.TableCellRenderer;
    import java.awt.*;
    import java.awt.event.ActionEvent;
    import java.awt.event.ActionListener;
    public class TableDialogEditDemo extends JPanel {
        public class ColorEditor extends AbstractCellEditor
                implements TableCellEditor,
                ActionListener {
            Color currentColor;
            JButton button;
            JColorChooser colorChooser;
            JDialog dialog;
            protected static final String EDIT = "edit";
            public ColorEditor() {
                //Set up the editor (from the table's point of view), which is a button.
                //This button brings up the color chooser dialog, which is the editor from the user's point of view.
                button = new JButton();
                button.setActionCommand(EDIT);
                button.addActionListener(this);
                button.setBorderPainted(false);
                //Set up the dialog that the button brings up.
                colorChooser = new JColorChooser();
                dialog = JColorChooser.createDialog(button, "Pick a Color", true,  //modal
                        colorChooser, this,  //OK button handler
                        null); //no CANCEL button handler
             * Handles events from the editor button and from the dialog's OK button.
            public void actionPerformed(ActionEvent e) {
                if (EDIT.equals(e.getActionCommand())) {
                    //The user has clicked the cell, so bring up the dialog.
                    button.setBackground(currentColor);
                    colorChooser.setColor(currentColor);
                    dialog.setVisible(true);
                    //Make the renderer reappear.
                    fireEditingStopped();
                } else { //User pressed dialog's "OK" button
                    currentColor = colorChooser.getColor();
            public Object getCellEditorValue() {
                return currentColor;
            public Component getTableCellEditorComponent(JTable table,
                                                         Object value,
                                                         boolean isSelected,
                                                         int row,
                                                         int column) {
                currentColor = (Color) value;
                return button;
        public class ColorRenderer extends JLabel
                implements TableCellRenderer {
            Border unselectedBorder = null;
            Border selectedBorder = null;
            boolean isBordered = true;
            public ColorRenderer(boolean isBordered) {
                this.isBordered = isBordered;
                setOpaque(true);
            public Component getTableCellRendererComponent(
                    JTable table, Object color,
                    boolean isSelected, boolean hasFocus,
                    int row, int column) {
                Color newColor = (Color) color;
                setBackground(newColor);
                if (isBordered) {
                    if (isSelected) {
                        if (selectedBorder == null) {
                            selectedBorder = BorderFactory.createMatteBorder(2, 5, 2, 5,
                                    table.getSelectionBackground());
                        setBorder(selectedBorder);
                    } else {
                        if (unselectedBorder == null) {
                            unselectedBorder = BorderFactory.createMatteBorder(2, 5, 2, 5,
                                    table.getBackground());
                        setBorder(unselectedBorder);
                return this;
        public TableDialogEditDemo() {
            super(new GridLayout());
            JTextField tf1 = new JTextField("tf1");
            add(tf1);
            JTextField tf2 = new JTextField("tf2");
            add(tf2);
            JTable table = new JTable(new MyTableModel());
            table.setPreferredScrollableViewportSize(new Dimension(500, 70));
            table.setFillsViewportHeight(true);
            JScrollPane scrollPane = new JScrollPane(table);
            table.setDefaultRenderer(Color.class,
                    new ColorRenderer(true));
            table.setDefaultEditor(Color.class,
                    new ColorEditor());
            add(scrollPane);
        class MyTableModel extends AbstractTableModel {
            private String[] columnNames = {"First Name",
                    "Favorite Color",
                    "Sport",
                    "# of Years",
                    "Vegetarian"};
            private Object[][] data = {
                    {"Mary", new Color(153, 0, 153),
                            "Snowboarding", new Integer(5), new Boolean(false)},
                    {"Alison", new Color(51, 51, 153),
                            "Rowing", new Integer(3), new Boolean(true)},
                    {"Kathy", new Color(51, 102, 51),
                            "Knitting", new Integer(2), new Boolean(false)},
                    {"Sharon", Color.red,
                            "Speed reading", new Integer(20), new Boolean(true)},
                    {"Philip", Color.pink,
                            "Pool", new Integer(10), new Boolean(false)}
            public int getColumnCount() {
                return columnNames.length;
            public int getRowCount() {
                return data.length;
            public String getColumnName(int col) {
                return columnNames[col];
            public Object getValueAt(int row, int col) {
                return data[row][col];
            public Class getColumnClass(int c) {
                return getValueAt(0, c).getClass();
            public boolean isCellEditable(int row, int col) {
                if (col < 1) {
                    return false;
                } else {
                    return true;
            public void setValueAt(Object value, int row, int col) {
                data[row][col] = value;
                fireTableCellUpdated(row, col);
        private static void createAndShowGUI() {
            JFrame frame = new JFrame("TableDialogEditDemo");
            frame.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
            JComponent newContentPane = new TableDialogEditDemo();
            newContentPane.setOpaque(true);
            frame.setContentPane(newContentPane);
            frame.pack();
            frame.setVisible(true);
        public static void main(String[] args) {
            javax.swing.SwingUtilities.invokeLater(new Runnable() {
                public void run() {
                    createAndShowGUI();
    }When you come back from choosing a color, tf1 is given the focus, instead of the table. This is because bringing the color picker window to the front causes a focus lost event for the cell editor component; it's temporary, as it should be, so why on earth is the system losing track of who has focus in the window??
    I see the following in Window#getMostRecentFocusOwner():
      public Component getMostRecentFocusOwner()
        if (isFocused())
          return getFocusOwner();
        else
          Component mostRecent =
            KeyboardFocusManager.getMostRecentFocusOwner(this);
          if (mostRecent != null)
            return mostRecent;
          else
            return (isFocusableWindow())
                   ? getFocusTraversalPolicy().getInitialComponent(this)
                   : null;
      }My app has a custom focus traversal policy, so I'm able to see who is being called, and indeed, getInitialComponent() is being called. Clearly, the KeyboardFocusManager is actually losing track of the fact that the table was focussed at the point where control was transferred to the color picker! This strikes me as completely unreasonable, especially since, as noted, this is a temporary focus loss event, not a permanent one.
    I'd be grateful for any wisdom in solving this, since similar behaviour to this little demo -- without focus loss, naturally -- is an essential part of my application.

    Looks like it is because the 'restore-focus-to-previous-after-modal-dialog-close' is in a later event than when the control returns to the action performed (which I guess makes sense: it continues the action event handler and the focus events are handled later, but I needed two chained invoke laters so it might also be that the OS events comes later).
    The following works for me (in the actionPerformed edited):
               // create the dialog here so it is correctly parented
               // (otherwise sometimes OK button not correctly the default button)
               dialog = JColorChooser.createDialog(button, "Pick a Color", true,  //modal
                            colorChooser, this,  //OK button handler
                            null); //no CANCEL button handler
                    //The user has clicked the cell, so bring up the dialog.
                    button.setBackground(currentColor);
                    colorChooser.setColor(currentColor);
                    button.addFocusListener(new FocusListener() {
                        @Override
                        public void focusLost(FocusEvent e) {}
                        @Override
                        public void focusGained(FocusEvent e) {
                            // dialog closed and focus restored
                            button.removeFocusListener(this);
                            fireEditingStopped();
                    dialog.setVisible(true);but a simpler request might be better (althoug I still need an invoke later):
    // rest as before except the FocusListener
                    dialog.setVisible(true);
                    button.requestFocusInWindow();
                    EventQueue.invokeLater(new Runnable() {
                        public void run() {
                            fireEditingStopped();
                    });And a quick fix to the renderer so you can actualy see the focus on it:
                    if(hasFocus) {
                        Border border = DefaultLookup.getBorder(this, ui, "Table.focusCellHighlightBorder");
                        setBorder(BorderFactory.createCompoundBorder(
                                border, BorderFactory.createMatteBorder(1, 4, 1, 4,
                                        ((MatteBorder) getBorder()).getMatteColor())));
                    }

  • JMenu doesn't dissapear when menu is losing focus

    Hello everyone!
    I have a JMenu with several JMenuItems. The problem is that the JMenu doesn't dissapear when the menu is losing it's focus, for example when I click somewhere in the application window. I use the Windows look and feel for my application.
    Any ideas ? Thanks.

    Add some try/catch block. My guess is that you bump in some NullPointerException.

  • Upgraded to Windows 8.1 Pro - new window is losing focus after while

    Hi,
    Just upgraded to 8.1 pro. When new window is opened (any application), after about 5-10 secs focus is lost. And again.... I have to click on window to regain focus. VERY ANNOING WHEN TYPING DOCO
    ANY SOLUTION MR MICROSOFT?
    1. Lodged problem with MS, but bo reply for 5 days
    2. Started reading posts on net - some about mouse behaviour got my attention
    3. Downloaded and installed latest drivers for Microsort mouse
    4. Unpluged 'old' mouse and plugged in new mouse(the same model
    5. Problem solved - no more problems with focus
    6. Conclusion - could ba a problem with Windows upgrade - mouse locked?

    For this problem, May be we can check Event Viewer if it identify the problem.
    In addition, try to make a clean boot or boot into Safe Mode to test whether this problem caused by 3rd problem, service or driver.
    For more details about Clean boot, please refer to the link below:
    http://support.microsoft.com/kb/929135
    Roger Lu
    TechNet Community Support

  • Window Loses Focus After Modal Dialog is Dismissed

    hi,
    I need a JDialog to be opened when i click on a button in JFrame.and it should be modal so that user must not get control to its parent window and rest of the windows can be accessed.
    So, i tried setting property like setModalityType(Dialog.ModalityType.DOCUMENT_MODAL), but still unable to access all the windows not only its parent until the dialog gets closed.
    Another issue i was facing is when i close out the dialog i need to get the parent to Front of other windows in application. But in my case it was not happening.After closing the dialog, i am getting the last focussed window to front but not its parent. I tried calling getParent().toFront() in windowClosing() Listener of that dialog, But still not able to solve the problem.
    Hope someone understands my problems and give me solution.
    Hoping for quick response and thanks in advance.

    shrikanthhyd wrote:
    I need a JDialog to be opened when i click on a button in JFrame.and it should be modal so that user must not get control to its parent window and rest of the windows can be accessed.
    So, i tried setting property like setModalityType(Dialog.ModalityType.DOCUMENT_MODAL), but still unable to access all the windows not only its parent until the dialog gets closed.Perhaps you can fix this by calling the first dialog either without a parent or not as a JDialog but rather as a JFrame. Then the second dialog's modality will not impinge on the visibility of the original parent window. For instance:
    import java.awt.Dimension;
    import java.awt.Window;
    import java.awt.Dialog.ModalityType;
    import java.awt.event.ActionEvent;
    import java.awt.event.ActionListener;
    import javax.swing.JButton;
    import javax.swing.JDialog;
    import javax.swing.JFrame;
    import javax.swing.JPanel;
    import javax.swing.SwingUtilities;
    class SwingFu2
        private JPanel mainPanel = new JPanel();
        public SwingFu2()
            mainPanel.setPreferredSize(new Dimension(400, 400));
            JButton showDlg1Btn = new JButton("Show Dialog 1");
            showDlg1Btn.addActionListener(new ActionListener()
                @Override
                public void actionPerformed(ActionEvent e)
                    showDlg1Action(e);
            mainPanel.add(showDlg1Btn);
        private void showDlg1Action(ActionEvent e)
            Window frame = SwingUtilities.getWindowAncestor((JButton)e.getSource());
            JPanel dlg1Panel = new JPanel();
            dlg1Panel.setPreferredSize(new Dimension(300, 300));
            JButton showDlg2Btn = new JButton("Show Dialog 2");
            showDlg2Btn.addActionListener(new ActionListener()
                @Override
                public void actionPerformed(ActionEvent e)
                    showDlg2Action(e);
            dlg1Panel.add(showDlg2Btn);
            //JDialog dialog1 = new JDialog(null, "Dialog 1", ModalityType.MODELESS); // either of these will work
            JFrame dialog1 = new JFrame("Dialog 1");  // either of these will work
            dialog1.getContentPane().add(dlg1Panel);
            dialog1.pack();
            dialog1.setLocationRelativeTo(null);
            dialog1.setVisible(true);
        private void showDlg2Action(ActionEvent e)
            Window window = SwingUtilities.getWindowAncestor((JButton)e.getSource());
            JPanel dlg2Panel = new JPanel();
            dlg2Panel.setPreferredSize(new Dimension(200, 200));
            JButton showDlg2Btn = new JButton("Show Dialog 2");
            showDlg2Btn.addActionListener(new ActionListener()
                @Override
                public void actionPerformed(ActionEvent e)
                    showDlg2Action(e);
            dlg2Panel.add(showDlg2Btn);
            JDialog dialog2 = new JDialog(window, "Dialog 2", ModalityType.DOCUMENT_MODAL);
            dialog2.getContentPane().add(dlg2Panel);
            dialog2.pack();
            dialog2.setLocationRelativeTo(null);
            dialog2.setVisible(true);
        public JPanel getMainPanel()
            return mainPanel;
        private static void createAndShowUI()
            JFrame frame = new JFrame("SwingFu2");
            frame.getContentPane().add(new SwingFu2().getMainPanel());
            frame.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
            frame.pack();
            frame.setLocationRelativeTo(null);
            frame.setVisible(true);
        public static void main(String[] args)
            java.awt.EventQueue.invokeLater(new Runnable()
                public void run()
                    createAndShowUI();
    Another issue i was facing I don't know on this one. Good luck.

  • Text Entry Box - On losing focus?

    Hello fellow Captivators.  I'm being thick-headed, I guess, but I'm trying to figure out how I might use the new feature of Text Entry Boxes on the Advanced tab:
    I tried the setting as in the graphic, then when I preview, I click in the text entry box to give it focus, then I tab out of it (focus shifted to the playbar), but nothing happens.
    Is this how it's supposed to work?  And I'd love some suggestions about how to use this new feature.
    Thanks very much.
    Mister C.

    Thanks for your insight, Rick.  It is as you say.  If I type a character in the TEB first, then the on focus lost action on the Advanced tab takes place.
    But it doesn't quite make sense to me.  I'm doing a little testing.  The more I test, the more confused I get!!!
    I configured a TEB with a Submit button.  On success, I set it to go to the next slide.  On the Advanced tab, I configured the on focus lost action to go to the previous slide.  Then I tried it ---
    If I type the correct text and click the Submit button, I'd expect the go to next slide action to take place.  Instead, since the focus was lost when I clicked the Submit button, it went to the previous slide.  If I type the incorrect text and click the Submit button, I'd expect to get incorrect feedback.  Instead, again, since the focus was lost when I clicked the Submit button, it went to the previous slide.  If I type correct text and use my shortcut key of Enter, the first Enter does nothing, then a second Enter executes the on success action and goes to the next slide.  But, if I type incorrect text and use my shortcut key of Enter, it shows incorrect feedback --- I assume because focus is not lost just by pressing Enter.  But --- this doesn't make sense either, because the help file says "On Focus Lost Select the action that should be performed when the user presses Enter or Tab, or moves the pointer away from the object."   If I configure the shortcut key to be Tab instead of Enter, regardless of whether I type correct or incorrect text, the on focus lost action happens and I go to the previous slide.
    So it looks like the Advanced tab on focus lost is taking precedence over the submit button validation process.  That is, except for the Enter key shortcut.
    Does this behavior match with your experience?   Or does it even make any sense?

  • Losing focus in Web Form

    I have the following problem:
    I have a form (B), which is a stacked canvas, which is called
    from another form (A). In the when-new-form-instance of (B) I
    execute_query and go_block to a block on (B). A visual attribute
    is set to highlight the current record (1) - this works. However
    if I select any record, say record (3), then the input focus
    seems to go to record (1), if I click again the focus, and
    current record attribute move to record (3).
    On client server the form works ok.
    I suspect this is a bug in the application server (3.??) or the
    appletviewer. However I suspect there may be a workaround.
    Ideas anyone ?
    Andrew Stubbs
    [email protected]
    null

    Sounds like a problem we had - Oracle Germany say its a
    jinitiator problem, that is solved in 1.1.7.11. According to the
    support matrix, you will also need to use the most recent
    patchset.
    - Matthew Cain
    Andrew Stubbs (guest) wrote:
    : I have the following problem:
    : I have a form (B), which is a stacked canvas, which is called
    : from another form (A). In the when-new-form-instance of (B) I
    : execute_query and go_block to a block on (B). A visual
    attribute
    : is set to highlight the current record (1) - this works.
    However
    : if I select any record, say record (3), then the input focus
    : seems to go to record (1), if I click again the focus, and
    : current record attribute move to record (3).
    : On client server the form works ok.
    : I suspect this is a bug in the application server (3.??) or the
    : appletviewer. However I suspect there may be a workaround.
    : Ideas anyone ?
    : Andrew Stubbs
    : [email protected]
    null

  • App switching in fullscreen mode: Losing Focus

    I have my mac running Mountain Lion (Ver 10.8.2) and have noticed that when switching between applications when fullscreen mode is involved that the application I am switching to loses focus.
    Scenarios:
    Switching from fullscreen app -> fullscreen app
    Switching from fullscreen app -> not fullscreen app
    Switching from not fullscreen app -> fullscreen app
    For all of the above scenarios when the switch is completed, the app I am switching to loses focus, but the application bar still shows the correct application name (so it doesn't just switch to Finder). This happens regardless of if I use a multitouch gesture or CMD+TAB to do the switch. Also, when this happens "CMD + ~" doesn't switch between windows of the application switched to.
    I would expect these scenarios to work the same as switching between regular applications where the one you switch to is in focus after the switch. Is this a bug with the fullscreen mode? or is there a setting I missed that can fix it? or is it a "feature"?
    I thank you for any help you can provide - this irritating bug makes it impossible for me to use fullscreen mode for my purposes.

    That was the problem! I had Live Wallpaper installed and running, so I guess I won't use that until there is an update to fix te problem.
    Thanks!

  • Minimising Games, and Losing Focus on HP Pavillion Phoenix h9-1191ea

    Hey, I recently bought a HP Pavillion Phoenix h9-1191ea Desktop PC and everytime I have a window open, it'll lose focus on it after a few minutes, and in the case of games, it'll minimise them completely. I would expect to see an error message, or another window after attention, but there's nothing. It returns me to the Desktop without a hint of an explanation, which means that I have to select it's icon on the Taskbar to continue playing. In the case of online gaming, this is particularly annoying. It's starting to drive me crazy.
    Any solutions?

    Hello AHook22,
    Sorry for the late reply. Sometimes threads can get lost and fall off my radar after a while.
    I don't think this is a hardware issue, but it's all the more likely that it could be. Before we can point to a hardware failure we have to rule out all software.
    By putting the computer into a clean boot state we removed any third party software from causing the issue, but it could be the operating system itself causing the issue.
    You may want to consider doing a recovery on the machine and starting over from scratch software wise. Then don't add anything else to the computer and see if the problem continues.
    Performing an HP System Recovery (Windows 7)
    If I have helped you in any way click the Kudos button to say Thanks.
    The community works together, click Accept as Solution on the post that solves your issue for other members of the community to benefit from the solution.
    - Friendship is magical.

  • Still Frames, Losing focus, PNG

    I'm put some still frames into my timeline, however, when I playback the stills, it loses focus. When I pause the timeline on the stills, it becomes fine, perfect focus and everything. (These stills are being taken from a seperate digital camera.)
    The stills I put in are jpg format...should they be in PNG format? How do I convert it to PNG format? Thanks in advance.
    I have:
    FInal Cut Pro 3.0
    Mac OS X 10.4.10

    Shane's Stock Answer #2: Blurry playback
    ONLY JUDGE THE QUALITY OF YOUR MATERIAL ON AN EXTERNAL NTSC MONITOR, OR AT LEAST A TV.
    1. Disable overlays on the canvas
    2. Make sure you've rendered everything (no green bars at the top of the timeline
    http://docs.info.apple.com/article.html?artnum=24787
    Video playback requires large amounts of data and many computations. In order to maintain frame rate and be viewable at a normal size, only about one-fourth of the DV data is used in displaying the movie to the screen. However, the DV footage is still at full quality, and is best viewed thru a TV or NTSC monitor routed thru your camera or deck.
    Shane

  • Window losing focus constantly.  Computer is unusable!!!!

    Help!  Ever since I upgraded to Mavericks, I have been having a problem where the window in any appllication that I am working in loses focus every few seconds.  I have read every forum I can find on the subject, but no one seems to have the answer to the problem.  The only thing that seems to work, but very unstable is launching my computer in safe mode.
    My brand new computer is unusable!!!!!!!!

    My brand new computer
    Apple>About This Mac>More Info>Service
    Please read the warranty paperwork that came w/your computer.
    You have 14 days to return the computer w/no questions asked. 
    You have 90 days of FREE phone tech support on top of your standard 1 year warranty unless you also purchased AppleCare which gives you an additional 2 years of coverage plus FREE phone support.
    Strongly suggest that you take FULL advantage of the above before it runs out.  Let Apple deal w/the problems.

Maybe you are looking for