Re: Updates in perllib API
On 18 Mar 2009 14:32:51 +1100, Scott Smedley wrote: > > Hi Mikhael, > > > most of the old API continues to work. > > Almost. > > No method add_defaultErrorHandler in FVWM::Module::Tk=HASH(0x9f8ae10) as > guessed from FVWM::Module::Tk::addDefaultErrorHandler at > /home/ss/fvwm/cvs.0/install.0/share/fvwm/perllib/FVWM/Module.pm line 684. This problem only existed for several minutes on my machine, then I fixed it by adding 'g' to regexp in Module.pm and Tracker.pm. But I needed to fix it in Module.pm.in instead. Ouch... > > Anyway, it is better to update user modules. > > FvwmTabs should be updated to the new API now. Ok. But it actually worked without this update on my machine. :) P.S. cvs diff/commit on my machine takes ages and timeouts (supposedly when huge ChangeLog is edited locally), so I need to move the files to another machine where cvs flies, but on that machine I can't run X... Regards, Mikhael.
Re: Updates in perllib API
Hi Mikhael, > most of the old > API continues to work. Almost. No method add_defaultErrorHandler in FVWM::Module::Tk=HASH(0x9f8ae10) as guessed from FVWM::Module::Tk::addDefaultErrorHandler at /home/ss/fvwm/cvs.0/install.0/share/fvwm/perllib/FVWM/Module.pm line 684. > Anyway, it is better to update user modules. FvwmTabs should be updated to the new API now. Scott.
Re: Updates in perllib API
Hi Mikhael, H, my previous reply seems to have gone astray ... > most of the old > API continues to work. Almost: No method add_defaultErrorHandler in FVWM::Module::Tk=HASH(0x9f8ae10) as guessed from FVWM::Module::Tk::addDefaultErrorHandler at /home/ss/fvwm/cvs.0/install.0/share/fvwm/perllib/FVWM/Module.pm line 684. > Anyway, it is better to update user modules. Ok. I updated FvwmTabs to the new API. Scott.
Updates in perllib API
Everyone who uses perllib please be aware of the updates in API. See the man pages ("fvwm-perllib man") and examples in tests/perl/README. However the basic old API (for main classes) should continue to work, i.e. for example addHandler or eventLoop are automatically dispatched to the canonical add_handler and event_loop methods. I didn't touch FvwmTabs on purpose, to demonstrate that most of the old API continues to work. Anyway, it is better to update user modules. Regards, Mikhael.