Below is an excerpt from a discussion I had with Marc Aurele La France concerning a 
scrolling issue under XFree86 with the -wm option. There are basically the following 2 
remarks:
1) Are there known issues with -wm that can cause scrolling problems (no 
update/drawing of newly exposed areas? Should a client be expecting this kind of [to 
me] unexpected behaviour, as Marc seems to suggest? (And what's the difference with 
the +bs option?)

2) Backing store is now by default off -- is that for performance reasons? In that 
case, would it be useful to make it controlable via e.g. xset? (One still has to 
"activate" it via CWBackingStore, right?)

Thanks (and sorry if this is overly long or off-topic!)
RenE Bertin

On Tue, 17 Sep 2002, RenE J.V. Bertin wrote:

> I have had some scrolling problems under X (4.0.1 and now 4.1.0) using an ATI Rage 
>Mobility
> adapter in my Dell Latitude CP450 laptop. In select applications, vertical scrolling 
>would *not*
> update/draw all or most of the newly exposed areas of the canvas/drawable, until an 
>explicit
> refresh was received. Notable example: opera (all versions), but also applications 
>using wxWindows
> (wxGTK).

> I finally discovered that this was due to the -wm "default whenmapped backingstore" 
>option passed
> to the server. Backingstore is possible, but one has to use +bs; with that option, 
>all is fine.

The driver has nothing to do with backing store.  +bs is a server option.
[...]

Marc.

n Wed, 18 Sep 2002, RenE J.V. Bertin wrote:

> 8-) This is a GTK bug as applications should be able to deal with any server,
> 8-) whether it implements backing store or not.

> True enough.  But what if the server's implementation of backing store
> is shaky?  Judging from the behaviour alone, this is what would appear
> to be the case when one selects the -wm form of backing store (the
> "WhenMapped default backing-store" as explained by XFree86 --help). BTW
> Opera for Linux is purely based on Qt.

Qt, GTK, whatever.  They're all the same to me.  In X client land.

> Why was the default set to off?  Performance?

I'm not familiar with the ins and outs behind that decision.  Ask about it
on [EMAIL PROTECTED]
_______________________________________________
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert

Reply via email to