This week's book giveaway is in the OO, Patterns, UML and Refactoring forum.
We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line!
See this thread for details.
The moose likes Swing / AWT / SWT and the fly likes When should the getLocation() be called Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

JavaRanch » Java Forums » Java » Swing / AWT / SWT
Bookmark "When should the getLocation() be called" Watch "When should the getLocation() be called" New topic

When should the getLocation() be called

Alec Lee
Ranch Hand

Joined: Jan 28, 2004
Posts: 569
In the javadoc for java.awt.Component.getLocation(), there is such a description:

Due to the asynchronous nature of native event handling, this method can return outdated values (for instance, after several calls of setLocation() in rapid succession). For this reason, the recommended method of obtaining a component's position is within java.awt.event.ComponentListener.componentMoved(), which is called after the operating system has finished moving the component.

But I don't understand what this statement means and if the call isn't reliable at all why it is there? If I dont want the trouble of using a listener, how should we use getLocation() to retreive the component's location?
I agree. Here's the link:
subject: When should the getLocation() be called
It's not a secret anymore!