About focus

I am moving our project from jdk1.3 to jdk1.4. And it's a puzzle that some component can not gain focus any more. So does anyone know what is the condition of obtaining the focus. For instance , I know , requestfocus() , setSelected() . I want to know all the other methods which can gain the focus. Thanks.

There is a new focusing model in 1.4. I'm surprised it affected your existing code though. Take a look at the new Focus API ( http://java.sun.com/j2se/1.4.2/docs/api/java/awt/doc-files/FocusSpec.html ).
Graeme

Similar Messages

Notification about Focus changes

Is ist possible to get notified about the change of focus, without registering my own focus manager at every component?

Hi,
I think there is no easier way to get around with this. FocusListeners need to be added to all your components. Since you just want to be notified about the change of focus between components, then basically your implementation of FocusListener will be the same for all the component. So, implement FocusListener once and use it in all the components, with just a line of code extra for each of the component.
component.addFocusListener(FocusListener);
Hope this helps. Please tell me if there is a better/shorter way to do it. =)
ChongWei

Problem About Focus transfer in swing JTable Cell

I open a JDialog in KeyPressed Event of Cell of the JTable,when the JDialog closed, I cannot set the Focus to next Cell in my code. the focus was set on the ToolBar(I don't write it in my code).
key pressed
void this_keyPressed(KeyEvent e) {
String text = this.getText().trim();
if(e.getKeyCode()==10 && text.trim().length()>0)
wzdlg = new JDialog();
Dimension dlgSize = wzdlg.getPreferredSize();
wzdlg.setLocation(0,0);
wzdlg.setModal(true);
wzdlg.pack();
wzdlg.show();
//When JDialog Closed,Focus move to next cell
               //table.editAt(0,1); //cannot getFocus
               //following cannot get focus too
     Component comp = ((DefaultCellEditor)table.getCellEditor(0,1)).getComponent();
     if (comp instanceof javax.swing.JTextField) comp.requestFocus();
Why? How Can I do?

Try calling prepareEditor after your editCellAt method. It would be like
JTable.editCellAt(row, col);
JTable.prepareEditor(theTextFieldComponent, row, col);
Here, the text field component would be from the component editor. I would recommend you holding a reference than doing a getComponent. But, both may work.

How I can receive information about focus on the JButton?

I create keyListener for Window. Then button OK has focus, method isSelected() returns false. I want know has button focus or no. How I can make it?

Hi,
if you want an answer to such a question, think of that, what you want to do - you want to listen to a focus event - so bring up the JButton documentation and search for "addFocusListener" and you will find, what you are searching for :)
greetings Marsian

Canon 6D Question about focus confirmation for manual focus lenses

I am very interested in the 6D. I own the 5D2 and concerning IQ there won't be much difference. But the loud and shaky shutter of the 5D2, the silent mode of the 6D respectively, lower weight, better ISO and smaller size would make the 6D a better camera. If I could have wished I wanted an even more purist and smaller 6D, no video, wifi and gps, however.
But I have a QUESTION: Will there be a focus confirmation on the focus points like the red confirmation flash there is with the 5D2? I like to shoot eg. with my small 40mm Voigtlander Ultron manual focus lens (just an excellent lens btw) and therefore highly appreciate this focus confirmation feature. If somebody already knows the answer, this would be very nice, thanks!
I got the impression Canon disadvantages manual focus lenses on their bodies, especially with the 5D3's new autofocus system (which is superb for autofocus lenses). Therefore I wish Canon would offer a reduced to the max fullframe body for manual focus shooters (what is a real passion for a growing number of photographers). Manual focus shooters need interchangeable focusing screens, focus confirmation on the focus point and live view. I guess Canon could be successfull with such a camera: the Canon IQ, especially the colors are excellent, the handling of a Canon is better than other brands, the overall package one gets with Canon is very good. There are so many outstandig MF lenses from Zeiss over Voigtlander to vintage lenses with adapters that are seeking the best FF body. And DSLR's are better than mirrorless cams but need to become smaller to make the size advantage of mirrorless cams irrelevant.
Thanks for reading, Dave.

The Canon 6D arrived today in Switzerland. The focus confirmation shows on the focus point and works well with Zeiss glass. We get the same focus finetuning like we had in the 5D2, what is important to align our Zeiss lenses. Besides, this is a nicely thought out camera. Smaller than one would expect from the factsheet numbers. The silent shutter mode is great. And there was a Hasselblad / Canon 6D comparison (beautyshooting), where I could not see a difference between the two on one of these big EIZO screens. The 6D is a reasonable camera, no show off factor. Better consider the 6D instead of the 5D3 if you are not a pro.

A question about focus or trend in oracle database releases

Hi,
I have a question on what is the focus or trend at a high level that can be seen in the way oracle has been delivering the data base. Among several things what can be summarized as a few technical focus areas. Can someone help? I think they are the following:
1) Focus on high availability (RAC,Data Guard)
2) Providing more and more features in the database (including oracle apex in database, regular expression support etc)
3) Exadata
4) Better managability with OEM
Can you help elaborate or suggest if this is appropriate?
Thanks

orausern wrote:
Hi,
I have a question on what is the focus or trend at a high level that can be seen in the way oracle has been delivering the data base. Among several things what can be summarized as a few technical focus areas. Can someone help? I think they are the following:
1) Focus on high availability (RAC,Data Guard)
2) Providing more and more features in the database (including oracle apex in database, regular expression support etc)
3) Exadata
4) Better managability with OEM
Can you help elaborate or suggest if this is appropriate?
ThanksI would echo what Sybrand has mentioned already. The way things are going , the focus is on two things IMO by Oracle. One, High Availability! Oracle corp wants to ensure with every upcoming release that the downtime , either planned or unplanned, must come down to its minimum value and there should not be almost anythign which would stop the business. There are tons of enhancements which we have seen in this manner and I am sure, there are going to be so many more upcoming.
Second is the need to ensure that database is not messed up by the human mistakes (and is going to be unavailable) . So that's why we are seeing more and more automated ways of handling/doing things. Now someone may say that its bad but I believe, it would take some time before it would be streamlined. It took 30 years for Oracle to come here so we shouldn't expect them to fix the automated database thingy in just two releases. Also, Oracle is focussing of giving a one-box-solution for almost all. So whatever you need, hardware, software, application and of course, database, you would get it all from one shop i.e. Oracle. The Exadata and Oracle's Enterprise Linux are going to be big helping factors in this thing.
Aman....

Focus in java.awt.robot

A couple of hours ago I read about java.awt.robot and I thought it was really cool.
Right now I have a working code that presses a couple of key and uses a listener to put them in the "messages" area of Borland JBuilder.
Is there any way to get these keys to be typed globally?
(ie. other programs read them as if the user was typing them.)
I haven't had much time to test out things like focus of the programs or messing with priorities in the task manager but any help would be appreciated =]
BTW, this isnt a hacking thing....just trying to make a program to automate tasks on my computer :)
~Thanks

Is there any way to get these keys to be typed
globally? Sure. The keys typed by robot can be received by other non-java apps.
I haven't had much time to test out things like focus
of the programs or messing with priorities in theor what about focus? Using the robot it's just like you'd normally focus on something; you click.
task manager but any help would be appreciated =]priorities in the task manager? In general you can't do anything in java about how the task manager prioritizes jobs. You can make your own internal threads higher or lower priority tho.

Focus events being received out of order

I have a complicated applet where each component is registered with multiple focus listeners. I have several pairs of JTextFields and JButtons - textfield A, button A, textfield B, button B etc. Clicking on a JButton normally causes a JTable to be popped and focus transferred to it. Clicking on the table header or selecting a table row causes the table popup to close and the focus transferred to the textfield associated with the button.
I'm running into a strange case where the focus is initially on textfield A. Clicking on button B causes a temporary loss of focus on textfield A. The trace shows that the focus owner is null and the permanent focus owner is textfield A. The table still gets launched. Selecting a table row causes it to close but no component has focus any more. Focus owner continues to be null, and permanent owner continues to be textfield A.
After working on other windows in the meantime, and returning to this window I find that the focus in now back to textfield B, as it should. However, the trace shows that B has received permanent focus events. This is followed by receiving permanent focusLost events on A and then permanent focusGained events on A. At the point all in said and done, the focus appears on B.
Does someone know why the focusGained event on B appears before focus events on A? Another strange thing in the trace was that some focus gain/loss method invocations were interrupted, another focus method invoked and the previous method resumed. I could possibly take care of this by using synchronized on all focus gain/loss methods. Also, some methods show only part of execution and not even resumed. This is still a mystery to me. I'll appreciate if someone can shed light on this.

One of the things you'll notice is that when a text field loses focus to a right-click JPopupMenu, it is never just one foucs lost/gained pair, but rather they trade focus back and fourth a few times. This is the same when the popup closes, the focus trades back and fourth a few times.
You are describing a similar situation between a button and a text field.
There never was any guarantee the gained/lost events happen in any order. Also, if there is a chain of focus events, the information in the intermediate events may not be useful.
If you really do need to understand the focus changes at an actionable level, you might want to consider writing a focus helper class that can be used to answer semantic questions about focus changes, such as, did this component lose focus because of a button click? Or was it a Popup? Or was it a Tab-keystroke?
The focus helper can store 'hidden' information in any JComponent using JComponent.setClientProperty(Object key, Object value)...
So instead of creating a focus listener like:
myComponent.addFocusListener(new FocusAdapter() {
public void focusGained(FocusEvent e) {
    // do stuff here
});You can do it like this:
myComponent.addFocusListener(FocusHelper.createTextFieldToButtonListener());and in that method it creates the listener like this (you might need to pass some parameters):
public static FocusListener createTextFieldToButtonListener() {
FocusAdapter adapter = new FocusAdapter() {
public void focusGained(FocusEvent e) {
    recordEvent(e);
    // do stuff here
return adapter;
}The helper method "recordEvent" tags those components with additional information about permenant and temporary focus ownership. Also it clears hidden information that is no longer useful.
Then later on you can give the focus helper a FocusEvent, and ask it, is this text field gaining focus because of a Tab-In, or is it because of a popup menu has closed?
The helper constructs answers based on the hidden properties it finds in the e.getOppositeComponent() and e.getSource(). It put those properties there, so it knows what they mean, and it uses them to distinguish between useless information in the focus event chain, and the important things you want to know.

Can someone explain how to set the focus to a component

Hello,
What is the best way to ensure that a component gets the focus with code. I have tried requestFocus and requestFocusInWindow and none of them seems to do there work. The frame containing the components that should get the focus is displayed, the component is focusable so that is not the problem. What I found out is that if the component is deep in a nesting of panes (where the top pane is in the frame) is that calling requestFocus or requestFocusInWindow does not give the component where this focus is called on the focus but either the pane that contains it, one of the parent panes of this pane or one of the components in these panes, in almost all cases the component requesting the focus does not get the focus at all. I always have to write a work around in defining a focus listener for all these panes that transfer the focus back to the component that requested the focus originally, I can't believe that this is the way to ensure that a component has the focus via code. I have searched for documentation but found nothing on what requestFocus(inWindow) is actually dooing (a lot about focus traversibility but I don't want to control this, just make sure that a component gets the focus).
Again I'm pretty sure that the toplevel window is activated and that the component that requested the focus is focusable (I had created a derived version of the DefaultFocusManager that showed who has focus). Personally I think (and I'm not alone if you do a search in this forum on focus management) that there is either a big problem in the documentation of focus management or that it is still not possible to even try to set the focus on a component in a easy way.
Marc

Hello,
thanks for your reply, here is some example code that illustrates the problem I have (the actual code is to big to show here, which is the raison why I did not posted it here). The code wil create a frame with a JPanel with a JTextField, a 'New' Jbutton and a 'Delete' Jbutton, a tabbed pane in the center ('New' will create a new JPanel, add it to the tabbed pane and set the focus on it, either by calling RequestFocusInWindow() directly or by calling it via InvokeLater (someone on this forum suggested to use this). I changed also the focusmanager to show the component that has the focus when you type something. To test compile and run the program (either with a call to requesteFocusInWindow directly or indirectly (by changing the comments), on my system I get the following behaviour:
1. requestFocusInWindow called directly
Start program en type, the tabbed pane has the focus
Press New and type something, a button has the focus not the created panel
Press New again and type something, a button has the focus not the created panel
2. requestFocusInWindow be called indirectly
Start program and type, the tabbed pane has the focus
Press New and type, the created panel has the focus (I thought at one moment that I had found the solution there, but alas ...)
Press New again and type something, a button has again the focus.
Note that with my real program it is not always a button that will have the focus, sometimes it is a combobox or a TextField (I tried to get this with the example code (the JTextField) but did not succeed.
Hopes this clarify the problem a little bid, what I want is when the window is visible to set focus on newly created panes (or in the real program on the panel that is selected via the tabbed pane or via a key combination to shift the focus between the panels) but requestFocusInWindow seems to behave unpredicatable. I can't imagine that what I see is a bug so I must make some assumptions which are not valid but I don't see them, btw listening on the WindowListener is I think not the solution because the frame is already displayed when I want to set the focus and I do not use a modal dialog box.
The example code follows here
Marc
* Main.java
* Created on December 21, 2004, 8:58 AM
package testfocus;
import javax.swing.*;
import java.awt.*;
import java.awt.event.*;
* @author marc
public class Main
static int counter;
/** Creates a new instance of Main */
public Main()
* @param args the command line arguments
public static void main(String[] args)
JFrame frm=new JFrame();
JPanel content=new JPanel();
frm.setContentPane(content);
final JTabbedPane paneContainer=new JTabbedPane();
JPanel bar=new JPanel();
JButton create=new JButton(new AbstractAction("New")
public void actionPerformed(ActionEvent ev)
counter++;
final JPanel pnl=new JPanel();
pnl.setName("test"+counter);
paneContainer.add(pnl);
pnl.setFocusable(true);
pnl.requestFocusInWindow();
/* Either use this or the previous line
SwingUtilities.invokeLater(new Runnable()
public void run()
pnl.requestFocusInWindow();
JButton delete=new JButton(new AbstractAction("Delete")
public void actionPerformed(ActionEvent ev)
int i=paneContainer.getComponentCount()-1;
if (i>=0)
paneContainer.remove(i);
JTextField dummy=new JTextField("Test");
bar.add(dummy);
bar.add(create);
bar.add(delete);
content.setLayout(new BorderLayout());
content.add(bar,BorderLayout.SOUTH);
content.add(paneContainer,BorderLayout.CENTER);
frm.setSize(300,400);
FocusManager.setCurrentManager(new DefaultFocusManager()
public void processKeyEvent(Component component,KeyEvent ev)
System.out.println("Focus owner"+getFocusOwner());
super.processKeyEvent(component,ev);
frm.setVisible(true);
}

Focus Inconsistency

was reading a problem from another user about focus in
regards to a textfield. I started to play around with it to learn a
bit more about it. I wrote the following little program and I ran
into an interesting problem. I should also say that you have to
have a UI Button in your library to get this to work.
When you start the program the textfield says "I got the
focus"
Click on the button once
textfield = I lost the focus to my_btn
button label = I've got the focus from my_txt
Click on the textfield
textfield = I've got the focus from my_btn
button label = I've lost the focus to my_txt
Click on the button again(sometime is takes another cycle)
textfield = I've lost the focus to undefined
button label = I've got the focus from undefined
Click on the text field
textfield = I've got the focus from my_btn
button label = I've lost the focus to my_txt
Click on the button again
textfield = I've lost the focus to undefined
button label = I've got the focus from undefined

What version of Aperture and of OS X?

Focus with JTable - JDK 1.4

Hi all, I wonder if there's anyone out there know about focus change on jdk1.4, please help me on this if you can:
with jdk 1.3, when I change focus between components on the same panel, I override this method of JTable to stop focus from being on table's rows only when the table has Focus since it does not move focus to the next component on the panel:
public boolean isManagingFocus() {
return false;
But when I use jdk 1.4 now, this method seems not work as expected anymore. The focus is now switch just between the rows when table has the focus and it does not move the focus to the next components on the panel when I hit TAB key.
If anyone knows how to fix this, please help me through. Anyhelp will be very appreciated.
CL

Sorry it's late but here goes.
isManagingFocus is deprecated in 1.4 so it's probably best not to use that anyway. It's also called from the constructor of JComponent so if it uses instance variables you might get things like NullPointerException if you're not careful.
I think the recommended way to approach it is to set the focus traversal keys something like this
// get your table from somewhere
JTable table = new JTable();
// use java.awt.AWTKeyStroke to set up the appropriate focus
// traversal keys
AWTKeyStroke tab = AWTKeyStroke.getAWTKeyStroke(KeyEvent.VK_TAB, 0);
AWTKeyStroke shiftTab = AWTKeyStroke.getAWTKeyStroke(KeyEvent.VK_TAB, KeyEvent.SHIFT_DOWN_MASK);
AWTKeyStroke ctrlTab = AWTKeyStroke.getAWTKeyStroke(KeyEvent.VK_TAB, KeyEvent.CTRL_DOWN_MASK);
AWTKeyStroke ctrlShiftTab = AWTKeyStroke.getAWTKeyStroke(KeyEvent.VK_TAB, KeyEvent.CTRL_DOWN_MASK | KeyEvent.SHIFT_DOWN_MASK);
// create a java.util.Set for forwards and backwards focus traversal
// keys. The actual concrete Set you use probably doesn't matter.
// I've used a java.util.HashSet
HashSet forwardKeys = new HashSet();
HashSet backwardKeys = new HashSet();
// add the appropriate keys to the appropriate sets
forwardKeys.add(tab);
forwardKeys.add(ctrlTab);
backwardKeys.add(shiftTab);
backwardKeys.add(ctrlShiftTab);
// set the focus traversal keys on the table.
table.setFocusTraversalKeys(KeyboardFocusManager.FORWARD_TRAVERSAL_KEYS, forwardKeys);
table.setFocusTraversalKeys(KeyboardFocusManager.BACKWARD_TRAVERSAL_KEYS, backwardKeys);

Where is the focus??

I have several applets on a page.
Under 1.4.0 I could see where the focus was & control it.
I am now using 1.4.1 and the focus is nowhere to be seen - I have put focus listeners in all of the components & the focus is gone from all of these by the time the applets finish loading.
I know there are a lot of posts about focus & 1.4.1, but none of them have helped.
I also know that there are changes with focus management in 1.4.1, but why would this mean that nothing has focus? Surely something must have the focus?
Thanks for any help.

Thanks for your input, however Java definitely lets you apply focus to yor applet.
I finally solved this, by finding out exactly where the focus was ending up - and it was ending up in one of the components in the main applet. This component is not even visible, and it's certainly not editable (it was the parent of the applet), so why the focus was going there, I don't know. So much for 1.4.1 fixing all the focus issues, though I must say the new API calls came in use in figuring this out.
Here is some duke $$ because you made an effort.

70d focus issue - admins answers please.

Will you admit that lot of 70d suffering focus issues?
Will you fix it by firmware update? Recall?
It's a big shame that everybody on the net speak about it and waste 1000 dollars and you just ignore us!!
I would like to get some answers please.
Thank you.

I have the same issue. It's odd, I've had the 70d since November-ish. I used to be a '2nd shooter' at weddings w/ just my olf Nikon d5100 & a 50mm 1.8 for portraits, and the kit lens for wides. Total N00b. .I started getting a grasp of things, and my wedding partner decided to double-book a bunch fo weddings. Since he was a Canon user, and I was looking for an upgrade to the 5100, I switched to canon & bought a 70D. Since then he's complained about focus issues, blaming me, and since i'm newer to this gig, took it to heart and assumed it was me. I have a steady hand, and believe to not be any kind of user error - I know how to shoot.
Today I discovered the 50+ pages of forum complaints on http://photography-on-the.net/forum/showthread.php?t=1354075 & the Canon forums http://forums.usa.canon.com/t5/EOS/When-will-canon-fix-the-focus-issues-with-the-70D/td-p/79330/page... - to find out that it might have been the camera all along? I just told the guy to screw off this weekend and quit because obviously I wasn't the photographer he needed... This focus problem hasn't been confirmed for me this week, but shooting w/ Tamron 17-50 2.8 & canon f4L 24-105, sure seems like theyr'e in the range of speculation here...
Will there be an update/recall to fix this?
Today I stumbled across a video (from the canon forums link) showing two photographers describing their issue w/ live view vs viewfinder view, and focusins on the center focal point for lenses 1.4-4.0... this sounds a LOT like my issue and am praying I can find an answer to this without having to call canon and RMA it.

70D focus shift in P Mode

I often shift the focal point using P shooting mode. Yet despite lots of research in the official manual and another manual, it's just not working. At most, it'll shift the aperature; not the focal point.
I've done this on every other Canon EOS I've owned, but can't seem to make the 70D do this. Any suggestions?

Program mode provides a unique feature called "program shift" -- not be confused with moving or shifting the selected focus point (that's completely different.)
When you shoot in full auto (green box) mode, the camera attempts to be more-or-less "idiot proof" in that it not only starts by automatically evaluating the shot and picking all camera settings... it also locks you out of making changes to those settings. In full auto mode you cannot change focus points, nor exposure settings, etc. It's all locked in and automatic.
When you use "program" mode, the camera starts out by automatically evaluating the shot and selecting exposure settings... except you can override these using "program shift".
For any given exposure, to correctly expose an image on the sensor the camera will need some amount of light. You can deliver light slowly over an extended period of time, or quickly in a very short time. You control this by changing the size of the aperture opening in the lens and the duration that the shutter will remain open. Many combinations of aperture and shutter speed will result in a delivery of the same amount of light.
But it turns out that the effect you get in the resulting image will not be the same even though the camera collected the same amount of light. Fast shutter speeds are great for freezing action. Slow shutter speeds are great for providing deliberate blur which can be used to "imply motion" in a shot. Small aperture sizes are great for creating a broad depth of field (the range of distances at which subjects appear to be in acceptable focus) whereas a large aperture is great for creating a tack-sharp subject with a deliberately blurred out background (and/or foreground if desired.)
But since "program" mode is more-or-less starting out like "automatic" you don't initially get to tell teh camera what you want with respect to aperture or shutter speed. This is where "program shift" comes in to play... you can half-press the shutter button to cause the camera to meter the scene... THEN you can roll the front dial (you do not need to keep your finger on the shutter) and the camera will shift the exposure... as you roll the wheel to the left it will use smaller apertures but increase the shutter exposure time. Roll it to the right and it will use larger apertures and faster shutter times.
This is not the same as "exposure compensation" in which you use the rear dial (not the front dial) to tell the camera to increase or decrease the exposure relative to what the meter reading indicates (asking the camera to deliberately over-expose or under-expose the shot.)
Meanwhile back to your question about focus points... as you look at the back of your camera, the button in the upper-right corner shows an icon (in white... not blue) of a rectangle with some focus point in it (the icon displays 5 points arranged in what is more or less a "+" shape even though your camera really has 19 AF points and they are not arranged like the icon shows... Canon uses that same icon on every EOS digital camera.) This is the "AF Point Selection" button. When you press that button you may move the selected AF point.
This feature is available in all of the "creative" modes (Program, Av, Tv, and M). It is not available in the other modes.
See page 105 of your manual to understand how this works.
The 70D also allows you to change the AF area selection mode (different than just selecting a single AF point) and you may wish to review all of the AF options available on your camera... I believe this whole section starts on page 99.
Incidentally... if the camera is allowed to use all of it's AF points to select focus (or if you are in one of the basic modes that don't allow you to control the AF point selection or mode) then the camera is programed to lock focus on the AF point which is able to achieve focus at the NEAREST focusing distance to the camera. E.g. Suppose you want to photograph a person, but there is a plant in your shot which is a bit closer to the camera than the person you intend to photoraph. If both subjects (person and plant) are covered by AF points, then the camera will ALWAYS choose the point which can lock focus at the nearer distance... and if that's the plant, then you'll get a nice sharp plant and an out-of-focus person.
Tim Campbell
5D II, 5D III, 60Da

D800-focus adjustment info in APERTURE image archive?

Hey dear friends,
I do not find under my picture metadatas the info about the focus adjustment of my lens/camera.
Downloading same picture into the NIKON VIEW software, this inof is available
In Aperture I expect this ino under EXIF-Infomation
Any help very wellcomed
Thnaks in advance
Franz-Josef
info from NIKON manual about focus adjustment

Hey Ernie
my mistake
I thought I answered you already, but I didn´t
Here attached three screenshots of the situation
      picture w/o focus ajustment ( off)
      picture with focus adjustement 0
      picture with focus adjustment -10
have a look in the third section : Kamerainformationen>> AF-Feinabst.:
Adjustment can be tuned in the range of +/- 20 for the body and for each lens
Is that what you have been looking for.
Any idea now, where to find this info in APERTURE?
Thanks and sorry for the late reply :-((
Best ergards
FJ

About focus

Similar Messages

Maybe you are looking for