| Ticket UUID: | 618096 | |||
| Title: | menu bugs with huge display (xinerama) | |||
| Type: | Bug | Version: | obsolete: 8.3.2 | |
| Submitter: | thomasafine | Created on: | 2002-10-03 14:45:33 | |
| Subsystem: | 12. Unix Menus | Assigned To: | tmh | |
| Priority: | 5 Medium | Severity: | ||
| Status: | Closed | Last Modified: | 2026-10-22 17:22:37 | |
| Resolution: | Works For Me | Closed By: | serhiy.storchaka | |
| Closed on: | 2026-10-01 11:55:33 | |||
| Description: |
(FYI, tk bug reporting is very well hidden from the tcl/tk home page) Environment: Solaris 8, openwin X11 server, CDE window manager (dtwm) I'm running X in "Xinerama" mode with one logical screen across two physical displays. To X clients, it appears as if there is one single 2560x1024 display. Both of the problems below occur when a Tk window is moved to the right half of the screen (into the second monitor), but it doesn't happen exactly at the same spot each time. Sometimes I can get a window fully into the right monitor, plus another 20 or 30 pixels without problems, but then if I move it farther to the right, the problems start. First, menus (at least within a menubar) become very slow and unresponsive. They don't respond at all to press-and-drag menu selection. Once started, this problem persists regardless of where the window is posistioned. Second when submenus of a menu are posted, they appear at the correct y, but far to the left, in the first monitor. This problem eventually goes away if the window is moved to the left again, but also not at a consistent x-position. I checked winfo: x, y, rootx, rooty, screenwidth, screenheight, pointerx, and pointery all return values that you'd expect for the main window regardless of where the window is. However when I post a menu with ".mb1.menu1 post 1800 120", and the immediately do "winfo rootx .mb1.menu1", it returns 520, which is 1800-1280, and 1280 is half the screen width, one monitor width. The menu still appears in the right half of the screen though. If I then call ".mb1.menu1 postcascade 2", the sub menu winds up (not surprisingly) at an x of 639, both visibly and as reported by winfo rootx. (winfo x reports the same as winfo rootx in these two cases also.) dtwm uses a "rooms" virtual window paradigm, so vrootx and vrooty should always be zero, and they are reported as such. vrootwidth and vrootheight are also reported correctly by winfo. | |||
| User Comments: |
serhiy.storchaka added on 2026-10-01 11:55:33:
Cannot reproduce with 8.4.15, 8.5.19, 8.6 and 9.1 on two monitors side by side, both with equal (1280x1024 + 1280x1024) and different resolutions (1920x1080 + 1280x1024 in both orders), with no window manager, mwm, twm, fvwm, openbox, icewm, metacity and xfwm4. With the window on the second monitor, a menu posted at x=1800 (in the reporter's layout) is placed at 1800, its cascade next to it, tk_popup places the menu where requested, and press-drag selection in the menubar works. 8.4.2 places the menus correctly too; its press-drag selection fails, but also on a single monitor. Menus are override-redirect windows, so the ConfigureNotify with coordinates relative to the second monitor in the reporter's trace came from the X server, most likely from the Xinerama implementation of the Solaris 8 server. thomasafine added on 2002-10-17 04:31:30: Logged In: YES
user_id=622568
I've traced it a bit through the code.
The value from Tk_X() changes from 1800 to 520 during the
execution
of:
TkPostTearoffMenu( )
TkWmRestackToplevel( )
WaitForConfigureNotify( )
since the last call doesn't actually do anything, I assume
the arrival
of an event actually causes the change, but I haven't found
that
handler for that event yet. If I have time to get back to
this I'll take
a closer look at XReconfigureWMWindow( ) -- either it is
being passed
bad information, or this is an Solaris Xlib bug. May be a
while before I
have time for that though.
| |||
Home
Timeline
Branches
Tags
Forum
Tickets
Download
Wiki