Moving shell does not move autocomplete drop down box

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create any autocomplete
2. Move the shell
3.

What is the expected output? What do you see instead?
Would expect it to hold it's place in the window, bu tit stays where it was

What version of the product are you using? On what operating system?

Please provide any additional information below.

Original issue reported on code.google.com by gareth.d...@gmail.com on 15 May 2007 at 11:01

[GoogleCodeExporter]

Need to find a listener so the JWindow knows when the JFrame has moved.

Original comment by don.cole...@gmail.com on 19 May 2007 at 7:58

• Changed state: Accepted
• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

I have attached a patch that applies to trunk (version 46), that introduces a 
common 
base class for Tips and Popups. For lack of a better name I called it 
ContextWindow. 
It adds the following behavior:

The popup will move with the window.
It is hidden when the window looses focus and redisplayed when focus returns, 
this 
avoids the case when switching to another window leaves the popup on top of it.
It is cleared when the window is resized, it probably won't be in the correct 
place 
anyway.

The window is specified in the constructor of Console and can be any 
java.awt.Window, this should make it easy to embed the console in any app. It 
can 
also be None, disabling this functionality.

I've tested it on Jython 2.2/Java 6 on Linux and Windows, I'm not sure about 
Jython 
2.1 but should be easy to fix if there are issues.

Original comment by and...@gmail.com on 18 Sep 2007 at 2:57

Attachments:

• contextwindow.patch

[GoogleCodeExporter]

The same problem occurs when the console window is closed while the popup 
window is
open. The completion window is left open then. Please raise the priority of this
issue. It is not just a minor cosmetic problem.

Original comment by Sven...@gmail.com on 3 Jul 2008 at 1:49

[GoogleCodeExporter]

The attached patch has a problem though. It accepts None for parentWindow and 
later
assumes that parentWindow would be a valid Component. This happens in 
particular in
ContextWindowListener.display() where self.parentWindow.locationOnScreen is 
accessed
without checking that parentWindow has been initialized.

Original comment by Sven...@gmail.com on 3 Jul 2008 at 2:18