Allan wrote:
>
> The only cases I can think of that need to have objects disabled are where
> a particular objects callback can cause some change to the document (such
> as the documentclass combo in FormDocument¹) but that can sometimes be
> blocked in the callback by checking the readonly status either of the
> buffer directly or of the bc_. In the documentclass case it needs to be
> disabled.
This is not true! Also changing the documentclass combo in FormDocument
does not change anything in the document! (well I was also of that opinion
before rewriting the code so be at ease that you're not the only one
misinterpreting this part of the code ;), what the callback does is only
set the default values of this document-class inside the dialog, which then
are only translated to the document if you press OK/Apply #:O)
Greets Jürgen
--
-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._
Dr. Jürgen Vigna E-Mail: [EMAIL PROTECTED]
Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253
I-39100 Bozen Web: http://www.sad.it/~jug
-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._
Have a nice diurnal anomaly.
