Subba Rao <subba9_at_cablespeed.com> writes:
> On 0, Dan Espen <dane_at_mk.telcordia.com> wrote:
> >
> > Thats going to be hard to do.
> > I just took your config file and removed the ModulePath
> > statement and autoraising worked fine.
> >
>
> I think I made some progress. Since the original fvwm/fvwm2 were installed
> using apt package manager I deleted them using apt. Then I compiled and
> installed the fvwm 2.5.5 version. One improvement is when I start the module
> "FvwmAuto 300" from my modules pop-up menu, then the AutoRaise feature works
> fine.
>
> Since I am invoking the FvwmAuto in the Init, why doesn't FvwmAuto start at
> that time. Here is my Init function:
>
> #
> # Stuff to do at start-up
> #
>
> AddToFunc "InitFunction"
> + "I" Module FvwmAudio
> + "I" Module FvwmAuto 300
> + "I" Module FvwmCommandS
> + "I" Module FvwmEvent
> #+ "I" Module FvwmButtons MiniButtons
> + "I" Module FvwmPager 0 0
> + "I" Module FvwmAnimate
> + "I" Module FvwmTheme
> < Other stuff >
>
> The same problem is true for the FvwmPager as well.
I don't know about the pager, but FvwmAuto started from the
init function for me.
In your module menu, you are missing the delay:
AddToMenu "Module-Popup"
+ "AutoRaise" Module FvwmAuto
I think you need the delay.
> > Of course I don't have the part thats read in with the
> > read command at the end and I'm not using debug.
> >
>
> What does this mean? Excuse my ignorance. :-)
This is at the end of the file you posted:
Read .fvwmrc-config
I don't have that file. There might be something in
that file that destroys the init function.
and in one post, you indicated that you started fvwm with
the "-debug" argument. I didn't use that.
--
Dan Espen E-mail: dane_at_mk.telcordia.com
--
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 Feb 19 2003 - 14:51:03 GMT