Hi there...
Comments below:
On Wed, Jul 10, 2002 at 10:37:41PM +0200, Dominik Vogt wrote:
> On Wed, Jul 10, 2002 at 10:22:33PM +0300, Tom Alsberg wrote:
> > <snip />
> > Well, I suppose this isn't the only buggy application.
> > Is it that much code to add for that?
>
> Yes. First a new style, the code to update windows on style
> changes, next we would probably add options to conditional
> commands, then someone will want to use the style in the
> WindowList and some of the modules, and so on. Just look at the
> flood of options to the conditinal commands compared with the
> options of the WindowList command and you know what I mean. Such
> things tend to grow without limits.
Oh... Well... Sounds logical...
> > <snip />
> > Yeah, I suppose... But they don't provide a solution for what I need
> > here, yet...
>
> That may be so. I'm readily willing to enhance the feature set of
> complex function, conditional commands and the like. This way,
> *all* the modules and the fvwm core benefit, not just one feeble
> module.
That's true...
> For example, take the PointerWindow command. Before I added it,
> there was no way to run functions on the window below the pointer.
> Today it's one of the most important conditional commands in my
> config. Without it, we could only dream of the autoraise
> functionality based on enter/leave events. But with it plus the new
> ENTER/LEAVE packets, implementing autoraising reduced to a couple of
> code lines. That's the way I like new features: small, doing a
> single task well, very flexible. Much better than ten new module
> options.
Also true...
> > > 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?
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.
So I suppose some-when it will be 'fixed', to its intended behavior -
not lowering windows when the pointer leaves them for the root
window. But that is not what I want (I want those windows lowered when
the pointer leaves the root window too).
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...
> > > > 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...
> > Thank you very much... I'm advancing (with lots of help from you and
> > the FVWM team) somewhat here...
>
> Discussions of this kind are one of the best ways to find out what
> we really need in fvwm. I wish everyone had the patience and
> endurance to continue them to a satisfying end.
Well, I want both to have my working environment convenient for me,
and FVWM to keep being the best window manager overall - my window
manager of choice - and keep getting better. It's already great, but
it can get yet even better, and there are always possibilities for
improvement.
> I appreciate your a lot. 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)...
> and perhaps even fvwm-theme.
I never yet took the chance to look at fvwm-theme... I will some-when
check it out and see better what it is about...
> Bye
>
> Dominik ^_^ ^_^
Thanks again,
-- Tom
--
Tom Alsberg - certified insane, complete illiterate.
e-mail: <alsbergt_at_softhome.net>
Homepage: http://www.cs.huji.ac.il/~alsbergt/
* An idea is not responsible for the people who believe in it.
--
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 majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Thu Jul 11 2002 - 13:18:27 BST