RE: [ jEdit-users ] sluggishness on dual monitors under Windows XP

[Zaleski, M. \(M.E.\) <mza...@fo...>]

=20

> -----Original Message-----
> From: jed...@li...=20
> [mailto:jed...@li...] On Behalf Of=20
> Steve Jakob
> Sent: Wednesday, August 11, 2004 2:59 PM
> To: jed...@li...
> Subject: Re: [ jEdit-users ] sluggishness on dual monitors=20
> under Windows XP
>=20
> On Wednesday 11 August 2004 13:22, Zaleski, Matthew \(M.E.\) wrote:
> > Yes it is a freakish new model.  It is a desktop replacement laptop=20
> > with a 1920x1200 LCD screen (it also has an Intel desktop chipset ,=20
> > 865? I'm not up on my Intel #s).  There are also analog and digital=20
> > VGA ports on the back that can be set to either replicate the LCD=20
> > screen or give you true dual monitor support.  I attach a=20
> 21" monitor running 1600x1200.
> > The extra real estate is great for software development.  I=20
> can keep=20
> > my IDE/jEdit up on one screen and help topics on the other.
>=20
> Ah, I see. I don't recall the other monitor being mentioned=20
> in your original message.
>=20
> 1920x1200 + 1600x1200 seems like a lot of graphics memory=20
> required, especially when you figure in double buffering. I'd=20
> be curious as to whether reducing the display resolutions=20
> might make a difference.
>=20
> Steve Jakob

Actually in 2d mode the graphics memory load is quite low (~32MB even
with double buffering at 32bit/pixel).  The video board has 128MB and
the system has 2GB of RAM.  On a lesser system, I could see your logic.
The counterpoint is that simply dragging the window off to the primary
and then back to the secondary restores full performance.

Today someone mentioned an open bug report with dual-monitor and jEdit.
Based on his report, it sounds like a Swing/JVM problem.  When I went to
Sun's bug database, there were a LOT of hits relating to crashing and
glitching on secondary monitors.  (jEdit is having graphical glitches
today too, prolly cuz I moved to the latest VM trying to track down the
problem.  I need to switch back to 1.4.1).  I guess I'm lucky that it is
reasonably stable at this point.

ATI boards and Sun JVMs have hated each other for quite a long time.
It's a crap shoot to find a VM version that doesn't have some issue with
the high performance boards.