This procedure pops up the standard binding dialog. There is one optional parameter, specifying the widget class which is to be manipulated. The difference to a widget specific binding configuration is that the bindings modified with this dialog are applied to all widgets of the currently selected class. Class bindings are not saved automatically. Instead, the developer can save the current class bindings into a general binding file. This file can be set with an XF option or a commandline switch. If there exist special class bindings, this file should be part of the distribution. If this is too complicated, there exists an option in the (Options | Source options) dialog to embed the class bindings into the created code.