On Wed, Jul 10, 2002 at 10:22:33PM +0300, Tom Alsberg wrote:
> On Wed, Jul 10, 2002 at 12:12:25AM +0200, Dominik Vogt wrote:
> > It's like taking a sledgehammer to crack a nut. All this
> > additional code just because of *one* buggy application?
>
> 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.
> > Complex functions already provide a far better solution.
>
> 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. 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.
> > 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? ;-)
> > > 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?
> 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. I appreciate your
a lot. Not only could we find a nice solution, but also came up
with a valuable addition to the FAQ and perhaps even fvwm-theme.
Bye
Dominik ^_^ ^_^
--
Dominik Vogt, dominik.vogt_at_gmx.de
Reply-To: dominik.vogt_at_gmx.de
--
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 Wed Jul 10 2002 - 15:38:10 BST