On Tue, 17 Oct 2000, Juergen Vigna wrote:
>
> 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)
Then the wording should be changed so its obvious that it's actually
changing the document yet. So instead of this broken English sentence:
"Should I set some parameters¹ to
article (Hebrew)
the defaults of this document class"
we could say something like:
"Should I use default settings for some parameters¹
if you choose to Apply this class change to
article (Hebrew)"
¹ Which parameters? Then we could make a more useful sentence.
Allan. (ARRae)
