Skip to content

BUG: Completion widget position and pager focus. #862

Closed
wants to merge 1 commit into from

2 participants

@prabhuramachandran

When the console widget is used with gui-completion, the positioning of
the completion widget was incorrect the first time a completion was
performed since the size of the widget is initially bogus. Using
sizeHint fixes this. If the paging mode is set to vsplit/hsplit, the
focus was lost after the pager is quit.

@prabhuramachandran prabhuramachandran BUG: Completion widget position and pager focus.
When the console widget is used with gui-completion, the positioning of
the completion widget was incorrect the first time a completion was
performed since the size of the widget is initially bogus.  Using
sizeHint fixes this.  If the paging mode is set to vsplit/hsplit, the
focus was lost after the pager is quit.
4f11d31
@fperez
IPython member
fperez commented Oct 13, 2011

Note: I can't reproduce the two problems you describe in my limited testing with PyQt. Perhaps the first is a function of window size/position on the desktop or size of the completion list itself. As for the second, I have no idea why I don't see the problem.

Having said that, I also don't see any problems with the code itself, and the explicit focus reset can't hurt even for those users who weren't seeing the problem. So I'm merging now, many thanks for the contribution!

@fperez
IPython member
fperez commented Oct 13, 2011

Merged (with rebase to avoid a recursive merge for just one commit), pushed.

@fperez fperez closed this Oct 13, 2011
@prabhuramachandran

The first seems to occur when the console is embedded into another application and can be triggered if the console is too close to the bottom of the screen. The second occurs when you have other widgets along with the console (only then would a loss of focus become painfully obvious). I guess I should have created a simple standalone app to demonstrate this. Thanks for merging regardless though, much appreciated!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.