You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently simple query windows in Tkinter (such as tkinter.simpledialog.askinteger()) are placed at position 50 pixels right and 50 pixels below of the top left corner of the parent widget (even if it is not visible). If the parent is not specified, the initial position was determined by a windows manager before bpo-1538878, after bpo-1538878 it was placed at position 50 pixels right and 50 pixels below the default root widget (even if it is not visible).
bpo-42630 restored the pre-issue1538878 behavior, but it is still has many quirks.
The proposed patch makes the placing algorithm similar to native Tk dialogs.
If parent is specified and mapped, the query widget is centered at the center of parent. Its position and size can be corrected so that it fits in the virtual root window.
Otherwise it is centered at the center of the screen.
I took a look at the somewhat messy popup placement in IDLE. The query.Query subclasses are centered over their parent. Some others are over the window but up and to the left. Maybe they have a custom geometry setting that I should delete. Search and replace dialogs are at the upper left of the screen. Bad if window is at the right edge. Editor SyntaxError boxes, with no placement specified, are centered on the screen. Centered on the text frame would be much better (as long as it did not cover the error). Same would be true of most anything else currently centered.
If parent is specified and mapped, the query widget is centered at the center of parent.
I am not sure what 'mapped' means. With patch, SyntaxError continues to be centered on screen even with editor visible and focused. Will say more on the PR.
Its position and size can be corrected so that it fits in the virtual root window.
I don't understand this. Will check the code.
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: