On Thu, Jul 11, 2002 at 09:17:41PM +0300, Tom Alsberg wrote: > > > > Right. The hack I made to inform FvwmAuto of the pointer entering > > > > the root window was too aggressive. I've modified it a bit and it > > > > should now cooperate nicely with gv. > > > > > > Cool... This seems to cooperate nicely with gv now, working just the > > > way I like it... This still does lower auto-raised windows when the > > > pointer leaves them for the root window though, but that's actually > > > what I want... So when that is fixed, I will want something to have > > > the current behavior again. > > > > You're pulling my leg, right? ;-) > > Well, what do you mean - pulling your leg?
Pulling somebody's leg means roughly to mislead someone for fun. > I am just saying, that now with -menter, it works the way I want it, > but that isn't exactly the way it should work, as documented in the > manual page. The man page is correct, but I did not mention that moving the pointer from any window into the root window now generates an ENTER_WINDOW packet too. FvwmEvents needs a notice about this behaviour too. [snip] > So unless something else is changed then, like the behavior with the > -menterleave option to workaround/fix the problem with gv and grabbing > the pointer, I will not have it the way I want, which is right now so > because -menter behaves a bit different than what's documented... Er, first you say that "it works the way I want it" and a few lines further down "So unless ... I will not have it the way I want"? So is the behaviour of -menter what you want or isn't it? Automatic lowering when entering the root window can be disabled by checking if the passed id is that of a real window or not (in other words: in the called functions without any changes to FvwmAuto). > > > > > Another weird thing, since updating from CVS a few days ago, FvwmPager > > > > > behaves a bit weird. Inactive windows (windows not having the focus) > > > > > have a black background, and look rather different than they used to > > > > > (they used to have the background color defined in the BackColor > > > > > style). > > > > > > > > Please update to the latest cvs. I've been working on the pager > > > > drawing code. > > > > > > I updated from CVS now, but it is still the same problem... > > > > Hm, you're probably running an old version of the module against > > a newer fvwm. Similar things often happen to me when module and > > fvwm version don't match. Are you sure FvwmPager got installed > > correctly? > > Well, I'm pretty sure... I listed the running processes after > restarting FVWM, and the FvwmPager which is running is the one > installed by the last make install (checked)... > Also now I tried building from scratch, removing any previous > installation I had locally, and installing of clean, being sure that > there wasn't any FvwmPager left somewhere before, it still looks that > way. > > Doesn't it happen for you? I checked, and even with the default > configuration (running as 'fvwm -f no-rc'), and nothing done except > popping up a pager, it looks different... Hm, default configuration. All my modules use colour sets. That effectively hides any windows with BackColor. Can you give an exact date for "a few days back"? Originally I thought this meant before the FvwmPager fixes I made, but I'm not so sure anymore. > > Not only could we find a nice solution, > > but also came up with a valuable addition to the FAQ > > I should (will now) look at the FAQ again and see what has changed / > been added (except for what I see when looking at the ChangeLog > files)... Nothing yet. I'll do that later. Bye Dominik ^_^ ^_^ -- Dominik Vogt, [EMAIL PROTECTED] Reply-To: [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]
