On 10 Feb 2006 08:35:04 +0100, Dominik Vogt wrote: > > On Fri, Feb 10, 2006 at 01:19:26AM +0000, seventh guardian wrote: > > Then we have two options: > > > > - Modules don't pass a matching string to fvwm and fvwm is entirely > > responsible of the module's aliases. > > > > - Modules continue to pass the matching string and fvwm translates it > > if an alias is defined in the core. > > Hm, would that break the old way FvwmIconMan requested its config > liens? I mean > > *FvwmIconMan*1*foobar ... > > Instead of the new > > *FvwmIconMan: 1 foobar ... > > Or is that completely transparent to the modules? > > Mikhael?
The second line is unfortunately (for backward compatibility with all other modules parsing their config) is sent as: *FvwmIconMan1 foobar ... FvwmIconMan simply supports 2 formats, old with "*", and without "*". Similarly, FvwmButtons config that looks like: *MyButtons: Frame 5 *MyButtons: (Container) is sent (again, for backward compatibility) as: *MyButtonsFrame 5 *MyButtons(Container) At least "DestroyModuleConfig MyButtons: Width" and "DestroyModuleConfig MyButtons: *" do the right thing, i.e. do not affect lines of another alias "*MyButtonsFrame: Title my-frame". Of corse, the correct thing is to introduce MX_MODULE_CONFIG packet and new rules (a module may request from the core a config related to the module name, say FvwmScript, or related to its alias, say FvwmButtons, or both, say FvwmForm) and to send the config lines without any prefix. This requires rewrite of all modules and the core. Not before 2.6. Regards, Mikhael.
