Jean-Marc Lasgouttes wrote:
> >>>>> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]>
> >>>>> writes:
>
> Juergen> How about a Paper Clip (TM) which pops up asking: "It seems
> Juergen> you want to insert a VSpace! May I help you?" A good and
> Juergen> approved method to prevent users from doing something ;-)
>
> Or, on a similar line, when the user selects Length, have an
> 'edit...' button which opens a popup where the user can set length
> and glue. THis way you (1) make things more complicated and (2) avoid
> to duplicate everywhere the code to set units and such.
Hm..., I do not like too many popups. And I'm not shure if we avoid
much duplication (we do of course concerning the GUI elements and
settings, though). We need to define the setEnable things anyway (for
the buttons then) and we don't have to set the units for every choice
explicitely, but we load a unit list with
fl_addto_choice(dialog_->choice_value_minus_above, units.c_str());
(and exclude some values if necessary).
I'm really not shure if we should try to force the user too much by
making things hard. We shouldn't make ugly things too easy, but IMHO
the better way is to *explain* the user why he should handle explicit
VSpace lenghts with care. So it is more a documentation issue.
> How difficult would that be?
I don't know. We'd need a new popup which is accessable from various
other popus (like FileDialog or MessageBox). So this would be something
like AskForText (no?). Apart from that I do not really like it, is this
not too much change for 1.2.0 (or are you talking about the bright
future)?
Other objections?
Juergen.
> JMarc
