Mikhael Goikhman wrote:
does outline move have to grab X? it seems like most evil thing (in context given context:-), turning nice multitasking system into a one task dos piece of crap, even if it's for few moments only (mostly).On 30 Nov 2002 15:52:05 +0100, Tor Stormwall wrote:When I for example play a movie and at the same time moving a window
the movie stops, so do the rest of the screen. Everything stops
completely. After I've moved the window to my wanted location
everything works fine again. The problem occurs not only when playing movies but all the times I
move something on the screen.
Do I need a special configuration or something?
I'm using the latest stable release of fvwm2 on a NetBSD 1.6 machine.The following should solve your problem: OpaqueMoveSize 200 The outline move, although a bit faster, grabs X, so don't use it if you run "real-time" updating applications (video, monitors).
the move could be excusable but the bigger problem is placement of new windows - if you have manual placement, the new window (e.g. browser popup add) stops the whole system (well, all X programs) from working. that's quite nasty. IIRC the placement of new windows always uses outline so your workaround wouldn't work. [yes, I know I can disable popups:-) that's not the point]
OT: am I the only one (ignorant of details of X internals:-) wishing grabbing the server was not introduced at all?
erik
--
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]
