Registration of callbacks is pretty simple. The function should take two arguments, the first is the FvwmModule instance, and the second is the packet object . For derived class methods, the names of the Fvwm packet types are used as keys for lookup . You can, of course, override this in your derived class. Sets the Fvwm event mask for the module.
Optional mask can be a bit-wise OR of Context values .
By default, the event mask is calculated automatically by searching for all implemented packet handler methods and registered callback handlers. If the Tkinter module has been imported, and at least one widget has been created, this will start the Tk mainloop. Note that currently, recursive mainloops with Tk doesn't seem to be working properly. The Packet class is not directly accessible by your code. Packet classes are named in a manner similar to derived method names, except that the word Packet is appended to the name, e.g. AddWindowPacket .