On 19 Dec 2008 18:02:16 +0000, Thomas Adam wrote: > > 2008/12/19 Yann Dirson <[email protected]>: > > > > We needed to trace and hook some actions to layer changes for e-Sidor[1], > > so here is the functionnality to do so. > > > > This patch also: > > * declare "restack" event to FvwmCommand > > * declare "reply" event to FvwmEvent > > * stop filtering out most extended messages for FvwmCommandS > > * minor whitespace cleanup > > > > We hope you'll find it useful. > > I suppose so -- although really detecting layer changes can still be > done via configure_window in FvwmEvent. > > Unfortunately this patch breaks perllib in FVWM. Please make ammends > to perllib/FVWM/Constants.pm to reflect your changes, and perhaps try > again. Oh, and some documentation, along with a complete Changelog > and an update to NEWS would be good.
I was not active on the list in 2008, so sorry for the late response. The answer about perllib was not very accurate. First, perllib/FVWM/Constants.pm is an autogenerated file (as well as Commands.pm in the same directory). If needed, "make regenerate" in this directory should recreate these files from the C sources. Second, when adding a new event type, it is not needed to touch perllib (unless you know perl and may verify your changes and want to canonize all argument names, like "old_layer", "new_layer"), someone else may do this. perllib is not broken at all when new event types are added, it just ignores unknown types (actually they are just not received, since the mask does not contain them). To make perllib aware of new event types after generating Constants.pm, the correct thing is to enhance EventNames.pm definition. Then to verify your addition, run "fvwm-perllib man events" and monitor these new events in FvwmDebug or FvwmGtkDebug. Regards, Mikhael.
