Richard Heck wrote: > With the introduction of modules came a distinction between the base class > and the document class. The former corresponds to the main layout file; the > latter is that plus the modules (or the document-specific layout, or > whatever else there could be). The way the code is now, the parameters for > GuiDocument come from the *document class*. So when we set the base class > in classChanged, we also need to recreate the document class---otherwise, > we still have the old one---and that's what the makeDocumentClass() class > call does.
this paragraph would be nice to have as docs somewhere in textclass if its not already there :) > So the parameters for GuiDocument now include the effects of loaded > modules. And what I'm not sure about is whether that is correct. If it is, > we have a different bug, namely, that adding or removing a module doesn't > update the document class. > > That said, can modules---and should modules---be able to affect what's > displayed in this dialog? what is the example of such an effect? pavel
