T
Tony Bonaccio
Guest
I am using Cadence 5141 on a Lenovo Thinkpad T60p with the ATI Fire GL
graphics chipset. I am running Linux RHEL 5 with the proprietary fglrx
video drivers from ATI. There's an annoying glitch in the redraw of Cadence
5141 windows with this setup - window redraw delays just long enough to
impact interactions like select, magnify, etc. The delay occurs on any
operation - open a new window, magnify, and so on. I notice it particularly
when opening a new schematic window, for instance, the schematic draws
quickly but the banner menus and sometimes the window boundaries take a
brief but annoying moment to draw. I see this in either KDE/kwin or
Gnome/metacity.
I have a sneaking suspicion that this has to do with the 8-bit pseudocolor
legacy. I have pseudocolor visuals disable and have tried the -use24
command line switch with no noticeable improvement. If I turn on the 8-bit
pseudocolor I see very strange window corruption. I have used IC61 a little
and don't see this problem at all.
Anyone experiencing anything similar? Any fixes or optimizations for this
kind of behavior? Thanks in advance.
Tony Bonaccio
Burlington, VT
graphics chipset. I am running Linux RHEL 5 with the proprietary fglrx
video drivers from ATI. There's an annoying glitch in the redraw of Cadence
5141 windows with this setup - window redraw delays just long enough to
impact interactions like select, magnify, etc. The delay occurs on any
operation - open a new window, magnify, and so on. I notice it particularly
when opening a new schematic window, for instance, the schematic draws
quickly but the banner menus and sometimes the window boundaries take a
brief but annoying moment to draw. I see this in either KDE/kwin or
Gnome/metacity.
I have a sneaking suspicion that this has to do with the 8-bit pseudocolor
legacy. I have pseudocolor visuals disable and have tried the -use24
command line switch with no noticeable improvement. If I turn on the 8-bit
pseudocolor I see very strange window corruption. I have used IC61 a little
and don't see this problem at all.
Anyone experiencing anything similar? Any fixes or optimizations for this
kind of behavior? Thanks in advance.
Tony Bonaccio
Burlington, VT