[EMAIL PROTECTED] writes: > On Sun, Feb 23, 2003 at 04:49:06PM -0500, Dan Espen wrote: > > Gert Brinkmann <[EMAIL PROTECTED]> writes: > > > Dan Espen wrote: > > > > > > >>- Mozilla refreshes its windows even if page 0 is not touched by the > > > >>screen. It would be enough to refresh the _visible_ windows only. > > > > > > > > This I don't see. On a 3x3 desktop, I have mozilla on one > > > > page. It slows down a little there, but not terribly. > > > > I've got 1.2b. > > > > > > Well, certainly i am not sure if it is really refreshing, because i > > > cannot see it when not currently shown on the screen. But this is the > > > only explanation i have why the pagers becomes so very slow. (When > > > moving around the mouse pointer a lot (perhaps 3 full cicles over all > > > outer pages) it takes about 3 or 5 seconds until the pager has finished > > > the screen-moving. In the meantime you can watch the screen moving > > > slowly on the former mouse-move-path. > > > > > > here: on a 3x3 desktop, mozilla 1.3b (did you mean this, or 1.2.1?) > > > > When I click on help->about, it says 1.2b. > > > > But, the problem isn't Mozilla, or FvwmPager. > > > > When fvwm executes a Scroll command, (which is what the pager > > generates), it's sending ConfigureNotify to windows that aren't > > visible. (When the window becomes actually visible it gets > > VisibilityNotify and Expose.) > > > > I don't think it should be doing the ConfigureNotify. > > It's required by the ICCCM :-/
I don't understand. The window is completely out of sight. Yet fvwm is sending it ConfigureNotify. -- Dan Espen E-mail: [EMAIL PROTECTED] -- Visit the official FVWM web page at <URL: http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
