Since upgrading from ion2 to ion3 on my computer at work, I've been
seeing odd behavior where the borders dividing frames are occasionally
shifted to the left or right.  I'm currently using 20050728 compiled
from source on XFree86 4.3.0, although I also saw this problem in
earlier versions of ion3 that I tried.  I haven't tried upgrading
again, as I haven't seen any mention of this in the changelog.  I
don't see this on my home machine, which is using similar versions of
ion3 installed from Debian packages.

I'm using NVidia's TwinView support (which provides Xinerama screen
info, I believe) to use two monitors side-by-side, each at 1600x1200. 
I've split each monitor into two side-by-side frames, and I usually
run xterms in each.

xwininfo reports that the xterm windows have a width of 796 pixels,
which translates to 88 columns with the font that I'm using.  I notice
several times a day that the sizes of the frames in one of the screens
shift, so that side-by-side xterms will be 87 and 89 columns, 86 and
90, or sometimes 87 and 88 (when the border between the frames just
moves by a fraction of a column).  For example, right now the left
frame on my left monitor has a width of 778 pixels (86 columns), while
the right frame is at 814 pixels (90 columns).  I haven't invoked any
resize commands that I would've expected to cause this.

I call WFrame.maximize_horiz() frequently and suspect it could be
related, although I have yet to find a way to reproduce the behavior
at will.  Sorry for how vague this bug report seems; let me know if
there's any other useful information I can provide.

On a side note, I've noticed that xdpyinfo often returns information
about a window other than the one that I clicked on.  I think I've
also seen this on my home machine, even when I was still using ion2. 
Is this a problem with ion, or with my X server or xdpyinfo?

Reply via email to