> The new release has lots of debugging output turned on during
> startup, and there is a sample buttonrc which can be used for
> testing. There is even instructions on how to install this separate
> from the old FvwmButtons, which probably is a good idea seeing
> that it simply will not work for some of you.
>
FvwmButtons-110396b.tar must be installed on top of
FvwmButtons-110396.tar; it is missing Fvwm.tmpl. After
that, compiling went well.
> Hope I haven't made any problems for you, but hey - it's not even in
> the beta yet :-)
>
I knew there was a reason I bound some menus to the left
mouse button in the root window. :-) I know what working
with software in development is like.
> I asked Chuck for this to get in the next fvwm beta, so please: let's
> hurry get that one last bug out of there before he decides its too
> risky..
>
OK, here's the report, testing with the included sample:
after making a minor change -- changing jball.xpm to one I
had -- the startup messages look fine, as far as they go.
They end with 'Creating windows...', and I don't get the
'OK' after it. Also, an xclock is created, but nothing
further happens.
I've tried removing the lines that swallow other programs
and get the same results, well, except for an xclock showing
up. Also, FvwmButtons is eating all the CPU it can while
it's hanging.
If a trace would really help, I can see if I can get it
to dump core in the morning. Or, maybe that's enough. Good
luck. Even though I don't need any of the improvements, I'd
like to see it work.
--RD
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Mon Mar 11 1996 - 22:32:36 GMT