On 03 Oct 2002 15:49:07 -0500, FVWM CVS wrote: > > Added files: > modules/FvwmDebug: FvwmGtkDebug.1 FvwmGtkDebug.in FvwmNewDebug.1 > FvwmNewDebug.in > > Log message: > * new modules FvwmNewDebug and FvwmGtkDebug, the text and graphical debuggers
I plan to remove the current FvwmDebug (and rename FvwmNewDebug) later unless you see a good reason not to. FvwmDebug is not currently up to date anyway and has some problems that FvwmNewDebug does not: * it requires maintaining * it does not support all argument types well (like pixels, booleans) * the output is not very readable/parsable FvwmNewDebug and FvwmGtkDebug are both fully generic, i.e. they will support any new/changed packets without modification. Of course for this to happen, structures in perllib/FVWM/EventNames.pm should be up to date, please actually update this file when you add/change current module packets. This class is used in all perl-based modules. In the future it may be auto-generated, but since Perl library is more complete in this respect than C module library, it is currently impossible. FvwmGtkDebug is not a regular static module, it is a pretty useful dynamical application, it requires Gtk-Perl installed, please test it. FvwmNewDebug does not require anything special. I plan to add more functionality to FvwmGtkDebug (Quit button :-), currently simply close a window) and FvwmNewDebug (--log file option). Both support setting the initial mask and xmask using command line options --mask and --xmask. The reason to leave FvwmDebug for now is for reference and since it currently has -w flag that is not yet supported. There is also a small problem with M_RESTACK arguments that I will solve in perllib soon. Regards, Mikhael. -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
