Juergen Vigna <[EMAIL PROTECTED]> writes:
| On 19-Mar-2001 Jean-Marc Lasgouttes wrote:
|
| > The problem I see is that we are supposed to be able to provide a
| > _string_ of htbp, not just one value. How do you plan to implement
| > that? I cannot think of a good UI for that, except maybe a list of
| > common reasonable option, to which we add a "custom" entry for
| > explicit modifiers.
|
| I guess the Form is a multiple selection form, what is missing (and
| you pointed this out) is an input-field for custom options!
I disagree. We write the floats to support the float.sty package (or a
better one if it exists) and the default floats in LyX. We should not
add code to cope with packages/paramters that we have never heard of.
If the user really needs that it can write ert.
| > A "use default" would indeed be useful for document-wide defaults.
|
| Well whatever, but isn't it that if you don't specify any particular
| option for a float "\float[options]" that automatically the document-wide
| options are assument, you don't have to say "\float[default options]".
| But If you insist then the default button should toggle all other buttons
| and also erase the custom-input field!
Yes. (except that the custom-input filed would not exist)
Lgb
