Lost focus problem. help.

I have a form contains two panels.
Left panel contains of a list of students, right panel contains of detail of the selected student.
When people modified student's info in right panel, I would like all info to be automatically saved to database.
I tried "focusLost" event, but it doesn't work.
seems like right panel is never focused.
Any suggestion how can I make it auto-save?
Thanks

The panel doesn't get focus. The fields in the component do. You could add listeners to all fields in the panel and when none of them have focus anymore, you could save all. Or you could save the data 1 field at a time.

Similar Messages

Camera (focus) problem - help?

Duplicate post, please see: Camera (focus) problem - help?
Message was edited by: Admin Moderator

Warranty is valid only in country of original purchase. You have to return
the iPhone to the US for evaluation. Either you return it personally or send
it to a friend/relative/co-worker in the US to take into Apple. Apple will not
accept international shipments for evaluation nor will Apple ship out of the
country after repair/replacement.
Have you tried the standard trouble shooting steps: restart, restore, restore
as new iPhone?

ALV Grid Handle Edit Event (Lost Focus)

Hi all,
I have some problems with the ALV Grid.
Target:
I have an ALV Grid with editable Column. If the user insert, update or delete the content of the column and leave the column (column lost focus) i'd like to do somthing - this means I need a event for this action. Can anybody help me to solve this problem?
Thanks Stefan

Use Event data_changed and data_changed_finished of the cl_gui_alv_grid.Then all you have to do is registering your event to the ALV and fill the methods with what you want to do.In ALV Grid, There is no event to capture the lost focus of a column if you don't modify it.
CLASS lcl_event_receiver DEFINITION.
    METHODS:
*$ Check the change
       handle_data_changed FOR EVENT data_changed
                               OF cl_gui_alv_grid
                           IMPORTING er_data_changed
                                     e_ucomm
                                     e_onf4
                                     e_onf4_before
                                     e_onf4_after,
       handle_data_changed_finished
                           FOR EVENT data_changed_finished
                               OF cl_gui_alv_grid
                            IMPORTING e_modified
                                     et_good_cells
                                     sender,
ENDCLASS.                    "LCL_EVENT_RECEIVER DEFINITION

JavaFX focus problem

Hi,
I have focus problem in JavaFX application. When I start the application main component has focus.
But if I switch between application by Ctrl + TAB and back to JavaFX application the component never gets focus again.
I tried to get focus on that component by TAB taster but it did not help.
Application code is very huge so I did send it to the post.
Thanks
Zlaja

"+How can I know which component has focus after main componet has lost it? +"
Perhaps loop on the components and check the 'focused' variable? Not very practical, I admit.
Note: Stage as a 'containsFocus' variable, too. It is false when another window is selected and true it is selected itself.
In my test, I request focus for a component. When the stage losts the focus, then regains it, the component regains the focus as well.

Re:Lost focus event

Hi all,
I have written some code in lost focus event.But the lost focus event is not firing.i didn't set any filters.please help me to sollve my problem.
Regards
Mohana

Hi,
try this
If pVal.ItemUid = "Uid" And pVal.EventType = SAPbouiCOM.BoEventTypes.et_LOST_FOCUS And pVal.BeforeAction = False and pval.charpressed=9 Then
end if
'9' is the item which gets fired when tab is pressed
it's better to write keydown if ur using tab
and coming to firing a event i gave the code before._refere to ur previous replie's_

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.

Focus problem since jre 1.4.2_11

Hi,
I have a awkward focus problem with my java applet. Everything is working fine for jre 1.4.2_10 and all older jre.
The applet is embedded in a large DHTML application running in a shell which uses the internet explorer for rendering. The applet communicates with the sorrounding java script via LiveConnect (JSObjects). We do use the static versioning, in order to determine the adaequate vm version. The controls are all based upon the swing controls, some are a bit modified.
Since the introduction of jre 1.5 update 6 the static versioning does no longer work properly. So, when I run my applet with 1.4.2_11 and all the predecessors a strange focus problem occurs.
When I click outside the applet (focus lost) and the click on a jscript control to get back the focus to the applet, the keyboard input does not reach the applet. The comboboxes do not work anymore. A mouse click is recognized, but the data-list which should appear is only flickering for a moment.
The only way to get the focus back, is to make a mouseclick on a selfmade datepicker (based on swing, implemeted like a popup-window). For sure, the large DHTML application is guilty, but definitely diffrent VM versions do behave differntly.
Does anyone has an idea, has seen similar effects or knows what has been changed in the jre between 1.4.2_10 and 1.4.2_11 ??
Any hint is appeciated! I am lost :-(((
cheers thorsten

Two things: Is there a document detailing manual removal of this JRE (and indeed others); you mention different 'builds' of the same JRE, this is the first time I have read that there are sub-versions/releases of a JRE. Where do I find out the available builds of this JRE and others and how they differ?

In Flex,how to make lost focus of textinput on enter click?

Hi
In Flex,how to make lost focus of textinput on enter click of keyboard ?
Thanks,
Sunil

Hi vibhuti,
I got your point but it will not helpful to me.
But I found solution ,When user clicks enter key make stage.focus = null so it will lost focus on text input and make focus in my current Alert Box.
Thanks,
Sunil

Focus problem in 1.4_2 after JPopupMenu show

Hi, there:
I have an application, with a JTextField when that textfield gained focus, a popup menu is shown, and when it lost focus, the popup menu is hidden.
My focus listener class is listed below, where popup is JPopupMenu, and function displayPopup() is just to call show() in JPopupMenu:
     class MyFocusListener extends FocusAdapter {
          public void focusGained(FocusEvent e) {
               System.out.println("focus gained.............");
               displayPopup();
          public void focusLost(FocusEvent e) {
               System.out.println("focus lost ..............");
               popup.setVisible(false);
     }Everything works fine in jdk 1.3 version. In jdk1.4_2 version, I met following issues:
1. whenever the text field gained the focus, the application keeps calling "focusGained()", and "focusLost()" functions endlessly (it seems the system keeps sending those focus events endlessly);
2. if I removed that "popup.setVisible(false)" in focusLost, then, it seems no other component can gain the focus anylonger.
So, very appreciated if anyone can give me some help, is that a bug in 1.4.2 or is there any way to work around?
Thanks a lot
David

The reason is that in 1.4.2 each time you show a popup over a text field, it trades focus back and fourth with the text field a few times (2-3 times) before it is fully shown.
That means you gain focus... diaplay a popup -> which fires 2-3 more gain/lost focus -> and on each of those, you show a popup -> infinite loop.
Here is the overall tip: Don't try to show/hide popups based on foucs events. Make them controlled by something else, like clicking events.
If you must do this, you can use a timer to avoid the issue. Just make sure you are using showPopup(Component,x,y) in your displayPopup() method!
class MyFocusListener extends FocusAdapter {
long lastTimeGainedFocus = -1L;
public void focusGained(FocusEvent e) {
    long currentTime = System.getCurrentTimeMilliseconds();
    if(lastTimeGainedFocus == -1L || currentTime - lastTimeGainedFocus > 100) {
      displayPopup();
    lastTimeGainedFocus = currentTime;
public void focusLost(FocusEvent e) {
     // do nothing here... popup should hide itself
}

Focus Problem on the t3i

My t3i is having focusing problems. What can be the cause? Can I fine to the focus like on the fullframe cameras?
Solved!
Go to Solution.

Kolourl3lind wrote:
OK I will but I just relized maybe it's because I am zooming after focusing and recomposing?
Yep - most lenses are "varifocal" -- meaning that if you carefully focus on a subject at some specific focal length in the zoom range... then zoom to a new focal length, then your subject will no longer be accurately focus. You must re-focus the lens.
There are a few lenses which are "parfocal" -- mean that if you zoom the focal length after focusing, your subject will still be accurately focused. However... VERY FEW lenses are technically "parfocal" (though some are close).
The lenses that I'm aware of which are "parfocal" are:
EF 16-135mm f/2.8L USM
EF 17-40mm f/4L USM
EF 70-200mm f/2.8L USM (only the non-IS version)
That's it. If you use any other lens, you have to re-focus the lens after zooming.
But I also notice you were shooting at 1/15th sec. That's a bit slow but you were at 18mm (which helps.) Here's the guideline on that.
In the 35mm days, there used to be a general guideline that if the shutter speed is equal to or faster than 1/focal-length (e.g. if shooting at 50mm the you'd want to be at least 1/50th sec.... at 70mm you'd want to be at least 1/70th or faster, etc.) would be adequate. This number doesn't apply to your T3i, but I'll get to that in a moment.
But there are a few caveats with that...
First, It assumes you are actually using very good camera-holding technique and you are actually TRYING to be steady. Good camera-holding technique means you are supporting the camera from below -- typically your left is palm-up supporting the bottom of the camera and lens and your elbow is in toward your chest/stomach. Your body weight is centered between your legs and you have a wide stance. This means you are not leaning so your muscles don't have to work hard to keep you upright and your arms work like a brace to support the camera to your body and of course your body is nicely balanced and stable.
Second, It's just a "guideline" -- not a rule. Some people are noticeably able to be more steady than others (and if caffiene makes you jittery and you just drank a coffee... and all that sort of thing.) And sometimes it takes a bit of practice to learn good technique.
Third, It's also not the same for APS-C size sensor cameras (like your T3i). For that camera, you'd have to multiple the minimum speed by the crop factor of the camera. For a Canon APS-C camera it's 1.6 (but if you wanted to use 1.5 that'd be pretty close.) That means at 50mm instead of using 1/50th you'd actually have to use 1/75th (technically 1/80th if we use the 1.6 factor). e.g. 50 x 1.6 = 80 so for 50mm we'd use 1/80th.
If you have a lens that includes image stabilization, then you may be able to shoot a bit slower.
Most image stabilization claims to improve lens stability by 2 to 4 "stops". What that means it that you can reduce the speed of the shutter... two to four times slower than you'd normally need because the lens is stabilizing for you. But more caveats apply because it's not as simple as "you get 4 stops". The stabilization isn't a guarantee... it's just a liklihood. If it has to be less ambitious to stabilize your shot it will be far more likely to succeed. If it has to be more ambitious to stabilize your shot then it'll do it's best... but there's no guarantee that it will work.
You were shooting at 18mm. So if you are using excellent posture and camera-holding technique but don't have image stabilization and you're the "average" person trying to hold the camera steady, then we multiply 18 x 1.6 and get 28.8. There is no 1/28.8th shuter speed so we'll round that to 1/30th (because there is a 1/30th.
1 stop slower than 1/30th is 1/15th.. and the image stabilization probably is adequate to get you 1 stop slower successfully.
2 stops slower is 1/8th. Image stabilization that claims "4 stops" will usually do well at 2 stops. So this is less of a sure-fire thing, but it does tilt the odds in your favor.
3 stops slower is 1/4 sec. At this point you're pushing the image stabilization system... you'll notice that if you shoot a lot of frames, that the "keeper" rate (good shots you like) will be lower, but you'll see that you are getting some.
4 stops slower is 1/2 sec (based on the base of 1/30th for an 18mm focal length on an APS-C size sensor camera). If you push any image stabilized lens to 4 stops, do not expect to get a very high keeper rate. It'll sometimes help you, but you have to accept that you're really being ambitious in your expectations.
That's image stabilization by the numbers... take the focal length, multiply it by your crop factor (which is always 1.6 but if you want to use 1.5 because it's a bit easier to do that math in our head it's close enough), round up to the nearest shutter speed available. If you have image stabilization you can speed up the shutter speed by 1, 2, 3, or 4 times faster... but each time you get more ambitious your odds of getting "keepers" go down (but it's still better than no image stabilization at all.)
The summary is that your minimum shutter speed (assuming good holding technique and that you are steady, etc. etc.) with image stabilization OFF the 1/30th would be your minimum speed. At 1/15h sec you were relying on 1 stop of image stabilization help. The image stabilization technology in the lens is good enought that "most of the time" it probably will be able to do this (not guaranteed... just likely.) If you were NOT using good posture and holding technique... you may be challenging your image stabilization system to try to keep up.
Tim Campbell
5D II, 5D III, 60Da

I've lost all my help files

Hi,
the other day when I started up LabVIEW I got an error saying it had to install a runtime engine, no idea why this happened but I fixed it by reinstalling my drivers. Anyway since I did that I've lost all my help files. The context help works fine, but when I click "VI, function and how-to help", or "Click here for more help" in the context help window, nothing happens. It doesn't even open up a window any more.
Any ideas what the problem could be? I'm not sure which disk the files are on so I'm not sure how to reinstall them.
I'm running LabVIEW 7.1 Full Development System on Windows 2000.
Thanks,
Nick

Hi Nick,
Sorry to hear about you losing the help files, which drivers did you re-install when you had the initial problem?
The help files are located in C:\Program Files\National Instruments\LabVIEW 7.1\help, you could check whether files in this folder have been deleted or your access has somehow been restricted to this folder. If there are a set of compiled HTML files there, try opening those individually and see if they open OK.
Can you open Help from the LabVIEW Help menu (Help>>Contents) or pressing F1?
I would try repairing LabVIEW from the Add/Remove programs section of the Control Panel first, and see if this helps.
Please let me know how you get on!
Mark
National Instruments UK & Ireland

Weird focus problems (& 1 workaround)

I am building a wizard with an extension of JDialog. Based on earlier input, I create the JDialog with a bunch of JPanels each with a combobox and a textfield. I have a next, cancel, and back button at the bottom on its own panel. I also have a "Finish" button when I reach the last panel. So I have to change the buttonPanel by putting the finish button on at the end and I put the next button back on when coming back from the last panel.
The problems I have been running into involve getting focus to one of the JTextfields mentioned above. I had a problem when I built my JDialog after clicking the next button. I removed everything from my ContentPane (cp) using cp.removeAll(). After building my JDialog, my code trys to give focus to the first text field. It wouldn't. I tested the text field and it is indeed focusable, visible, and displayable.
The fix was removing each individual component from the content pane instead of doing the removeAll(). Then, after adding everything to the content pane, my textfield could grab the focus.
The only problem that remains is with the back button. When I move back from the final panel the following code is executed:
buttonPanel.removeAll();
//buttonPanel.remove(backButton);
//buttonPanel.remove(finalButton);
//buttonPanel.remove(cancelButton);
buttonPanel.add(backButton);
buttonPanel.add(nextButton);
buttonPanel.add(cancelButton);
Then, as in other cases, the buttonPanel object is added to the content pane. This causes the textfield to be unable to grab focus. I commented out the code and the focus worked fine (but of course my buttonPanel was not correct).
This is happening with 1.4.1 on windows 2000. I don't have another computer to test this one.
Am I doing something inherently wrong or is this a bug?
I've looked around and there are a lot of problems reported with focus and swing, but I wasn't sure if this was a symptom of those problems or if this is something different.
I appreciate any help you can give.
thanks,
Geoff

I won't throw everything at you but this should be plenty. If anyone needs any explanations I am not going anywhere. I'm trying to figure out if the problem is a bug or not.
The workaround is mentioned in a comment for the action listener of nextButton. The problem piece of code that is mentioned at the top of this thread is also commented and it is part of the action listener for backButton.
There are some declarations I have left out and I've left out some helper functions and some private classes, but I looked at it closely. There shouldn't be anything that is a mystery here. But, again, if anything is unclear just give a shout.
thanks in advance,
Geoff
public InfoDialog(JFrame owner, int[] results)
     super(owner, "Wizard", true);
     cp = getContentPane();
     this.owner = owner;
     answers = results;
     lastPanel = answers.length-1;
     //figure out number of panels and last one greater than 0
     for(int i =0; i<answers.length; i++)
          numPanels++;
          if(answers>0)
               lastPanel = i;
     if(numPanels==0)
          return;
     nameVectors = new Vector[answers.length];
     typeVectors = new Vector[answers.length];
     while(answers[currentPanel]<=0 && currentPanel<answers.length)
          currentPanel++;
     firstPanel = currentPanel;
     inputLabel = new JLabel();
     inputLabel.setAlignmentX(Component.CENTER_ALIGNMENT);
     inputLabel.setText(getInputLabelText(currentPanel));
     panelArray = new JPanel[answers[currentPanel]];
     nameVectors[currentPanel] = new Vector();
     typeVectors[currentPanel] = new Vector();
     comboArray = new ClassComboBox[answers[currentPanel]];
     textArray = new StringTextField[answers[currentPanel]];
     for(int i=0; i<panelArray.length; i++)
          panelArray[i] = new JPanel();
          panelArray[i].setLayout(new BoxLayout(panelArray[i], BoxLayout.X_AXIS));
          comboArray[i] = new ClassComboBox();
          panelArray[i].add(comboArray[i]);
          textArray[i] = new StringTextField(new String(""));
          panelArray[i].add(textArray[i]);
     cp.setLayout(new BoxLayout(cp, BoxLayout.Y_AXIS));
     //cp.add(infoPanel);
     cp.add(inputLabel);
     for(int i=0; i<panelArray.length; i++)
          cp.add(panelArray[i]);
     //infoPanel = new JPanel();
     //infoPanel.setLayout(new BoxLayout(infoPanel, BoxLayout.X_AXIS));
     //infoPanel.add(new ClassComboBox());
     //infoPanel.add(new StringTextField(new String("")));
     //cp.add(infoPanel);
     backButton = new JButton("Back");
     backButton.setEnabled(false);
     backButton.addActionListener(new ActionListener(){
          public void actionPerformed(ActionEvent ae){
               //save values of previous panel into vector
               typeVectors[currentPanel] = null;
               nameVectors[currentPanel] = null;
               typeVectors[currentPanel] = new Vector();
               nameVectors[currentPanel] = new Vector();
               for(int i=0; i<panelArray.length; i++)
                    typeVectors[currentPanel].add((String)comboArray[i].getSelectedItem());
                    nameVectors[currentPanel].add(textArray[i].getText());
               //remove everything from JDialog
               //cp.removeAll();
               cp.remove(inputLabel);
               for(int i=0; i<panelArray.length; i++)
                    cp.remove(panelArray[i]);
               cp.remove(buttonPanel);
               //store last panel, figure out what the new currentPanel val is
               int previousPanel = currentPanel;
               currentPanel--;
               while(answers[currentPanel]<=0 && currentPanel >= firstPanel)
                    currentPanel--;
               //go through panelArray getting rid of its subcomponents
               for(int i=0; i<panelArray.length; i++)
                    panelArray[i].removeAll();
               panelArray = null;
               comboArray = null;
               textArray = null;
               //arrays will be initialized to the appropriate length for the currentPanel
               panelArray = new JPanel[answers[currentPanel]];
               comboArray = new ClassComboBox[answers[currentPanel]];
               textArray = new StringTextField[answers[currentPanel]];
               //inputLabel.setText(pinTypes[currentPanel]);
               inputLabel.setText(getInputLabelText(currentPanel));
               cp.add(inputLabel);
               for(int i=0; i<panelArray.length; i++)
                    panelArray[i] = new JPanel();
                    panelArray[i].setLayout(new BoxLayout(panelArray[i], BoxLayout.X_AXIS));
                    comboArray[i] = new ClassComboBox();
                    comboArray[i].setSelectedItem(typeVectors[currentPanel].get(i));
                    panelArray[i].add(comboArray[i]);
                    //textArray[i] = new StringTextField(new String(""));
                    textArray[i] = new StringTextField((String)nameVectors[currentPanel].get(i));
                    panelArray[i].add(textArray[i]);
                    cp.add(panelArray[i]);
               //focus problem is caused by this block of code
               //moving back from last panel
               if((currentPanel == lastPanel-1) && previousPanel==lastPanel)
                    buttonPanel.removeAll();
                    //the following code did not fix the problem
                    //buttonPanel.remove(backButton);
                    //buttonPanel.remove(finalButton);
                    //buttonPanel.remove(cancelButton);
                    buttonPanel.add(backButton);
                    buttonPanel.add(nextButton);
                    buttonPanel.add(cancelButton);
               if(currentPanel==firstPanel)
                    backButton.setEnabled(false);
               cp.add(buttonPanel);
               //System.out.println();
               //System.out.println("textArray[0].isVisibile: " + textArray[0].isVisible());
               //System.out.println("textArray[0].isDisplayable: " + textArray[0].isDisplayable());
               //System.out.println("textArray[0].isFocusable: " + textArray[0].isFocusable());
               //textArray[0].grabFocus();
               pack();
               //repaint();
               System.out.println();
               System.out.println("textArray[0].isVisibile: " + textArray[0].isVisible());
               System.out.println("textArray[0].isDisplayable: " + textArray[0].isDisplayable());
               System.out.println("textArray[0].isFocusable: " + textArray[0].isFocusable());
               textArray[0].grabFocus();
     nextButton = new JButton("Next");
     nextButton.addActionListener(new ActionListener(){
          public void actionPerformed(ActionEvent ae){
               //logic to grab information from JComboBox and JTextField
               typeVectors[currentPanel] = null;
               nameVectors[currentPanel] = null;
               typeVectors[currentPanel] = new Vector();
               nameVectors[currentPanel] = new Vector();
               for(int i=0; i<panelArray.length; i++)
                    typeVectors[currentPanel].add((String)comboArray[i].getSelectedItem());
                    nameVectors[currentPanel].add(textArray[i].getText());
               //here is the code that didn't work and the subsequent code
               //that fixed the problem
               //cp.removeAll();
               cp.remove(inputLabel);
               for(int i=0; i<panelArray.length; i++)
                    cp.remove(panelArray[i]);
               cp.remove(buttonPanel);
               currentPanel++;
               //System.out.println("currentPanel prior to processing: " + currentPanel);
               if(currentPanel<(answers.length-1))
                    while(answers[currentPanel]<=0 && currentPanel<lastPanel)
                         currentPanel++;
               for(int i=0; i<panelArray.length; i++)
                    panelArray[i].removeAll();
                    //comboArray[i].removeAll();
                    //textArray[i].removeAll();
               panelArray = null;
               comboArray = null;
               textArray = null;
               panelArray = new JPanel[answers[currentPanel]];
               inputLabel.setText(getInputLabelText(currentPanel));
               cp.add(inputLabel);
               //test to see if this is the first time reaching this point
               //if you haven't reached this point before, vector will be null
               boolean firstTime = false;
               if(nameVectors[currentPanel]==null)
                    firstTime = true;
               if(firstTime)
                    nameVectors[currentPanel] = new Vector();
                    typeVectors[currentPanel] = new Vector();
               comboArray = new ClassComboBox[answers[currentPanel]];
               textArray = new StringTextField[answers[currentPanel]];
               //establish the proper # of combo boxes & text fields
               int len = panelArray.length;
               for(int i=0; i<len; i++)
                    panelArray[i] = new JPanel();
                    panelArray[i].setLayout(new BoxLayout(panelArray[i], BoxLayout.X_AXIS));
                    comboArray[i] = new ClassComboBox();
                    if(!firstTime)
                         comboArray[i].setSelectedItem(typeVectors[currentPanel].get(i));
                    panelArray[i].add(comboArray[i]);
                    textArray[i] = new StringTextField();
                    if(!firstTime)
                         textArray[i].setText((String)nameVectors[currentPanel].get(i));
                    panelArray[i].add(textArray[i]);
                    cp.add(panelArray[i]);
               if(currentPanel==lastPanel)
                    buttonPanel.removeAll();
                    buttonPanel.add(backButton);
                    buttonPanel.add(finalButton);
                    buttonPanel.add(cancelButton);
               backButton.setEnabled(true);
               cp.add(buttonPanel);
               //textArray[0].requestFocus();
               //System.out.println();
               //System.out.println("textArray[0].isVisibile: " + textArray[0].isVisible());
               //System.out.println("textArray[0].isDisplayable: " + textArray[0].isDisplayable());
               //System.out.println("textArray[0].isFocusable: " + textArray[0].isFocusable());
               //textArray[0].grabFocus();
               pack();
               //System.out.println();
               //System.out.println("textArray[0].isVisibile: " + textArray[0].isVisible());
               //System.out.println("textArray[0].isDisplayable: " + textArray[0].isDisplayable());
               //System.out.println("textArray[0].isFocusable: " + textArray[0].isFocusable());
               textArray[0].grabFocus();
     setLocationRelativeTo(owner);
     setVisible(true);

[SOLVED] Google Chrome doesn't render page after lost focus in Awesome

Hello !
I have installed fresh Arch Linux with linux-ck and awesome. After that I have installed google-chrome-stable and started it. Everything works well, but if I opened other application (chrome lost focus) and then got back to the chrome, it freezes. Mouce cursor worked as expected (cursor changed after hovering link, input field, etc) but view was not updated.
Everything works well again if I change desktop to the second and go back to the first again (mod+2, mod+1). Chrome works, responses etc well.
bvg
Did you met something like that ? How can I fix it ?
Edit:
I bet this issue has something in common with hw acceleration. If I run some game on steam, lost focus, got back to the game - it show last rendered screen before focus has been lost (sound is ok, game is responsible but not updates screen).
I use nvidia. Do I need some extra configuration to handle it ?
Last edited by hsz (2013-12-18 17:16:17)

The problem was `xcompmgr` which caused "freezing" view. I switched it to `unagi` and all of the problems have gone.

How to catch cell lost focuse event of matrix

Dear all
can you tell me how to catch the cell lost fouc event of matrix.
i want to check the value is entered the that cell, which is not greter than the extising value..
thanks in advance......

Hi
For that you can use either validate or lost focus event
Private Sub SBO_Application_ItemEvent(ByVal FormUID As String, ByRef pVal As SAPbouiCOM.ItemEvent, ByRef BubbleEvent As Boolean) Handles SBO_Application.ItemEvent
        ' BubbleEvent sets the behavior of SAP Business One.
        ' False means that the application will not continue processing this event.
        ' Validate event
        If (pVal.FormType = 133) And (pVal.ItemUID = 38) And (pVal.ColUID = 1) And _
          (pVal.EventType = SAPbouiCOM.BoEventTypes.et_VALIDATE) Then
            If (pVal.Before_Action) Then
                'write your code
            End If
        End If
        'Lost focus event
        If (pVal.FormType = 133) And (pVal.ItemUID = 38) And (pVal.ColUID = 1) And _
         (pVal.EventType = SAPbouiCOM.BoEventTypes.et_LOST_FOCUS) Then
            If (pVal.Before_Action) Then
                'write your code
            End If
        End If
    End Sub
Hope this helps
Regards
Arun

My apple 4 lost, I get so sad. service can help check it repair somewhere in Shaanxi province of China, Xi'an city lost, I need help.

My apple 4 lost, I get so sad. service can help check it repair somewhere in Shaanxi province of China, Xi'an city lost, I need help.
<Personal Information Edited by Host>

Does [this firmware update|http://www.apple.com/downloads/macosx/apple/firmware_hardware/imacefifir mwareupdate13.html] apply to your machine? If so, putting it on may fix the boot from DVD problem.

Lost focus problem. help.

Similar Messages

Maybe you are looking for