"Bo Peng" <[EMAIL PROTECTED]> writes: >> If you can get it to work properly, this is definitely the way to go. >> This shall be done for unknown classes and for unknown layouts. > > I have it almost working here, but there are some subtle problems such > as when two 'article' documents having some different 'unknown' > layouts. Currently, the extended layout list is displayed for both > documents, which means a regular article can use a unknown layout from > another document. This seems wrong but a proper solution is hard to > find.
I do not really understand why you need to create several unknown layouts. Each textclass should have its own. The problem, as as see it, is only with the display of layouts in the combo. This should be solved at interface level. Alos, now that I have re-read your message, I do not think that hasLayout() should be removed. Some parts of the code need to be aware of which layouts are there. JMarc
