Bo Peng wrote:
I think the proper way to solve any option would have been to outsource
the option definitions in a text file which is easily upgradable.
But then 1.5.0 will not be usable for listings 2009... Adding a
backdoor is always safer. :-)
First strict validation, and then a work-around in case
the validation is no longer correct. This seems complicated.
How about relaxing the validation then, so the user isn't _forced_
to enter valid input? Then there is no need at all for
a workaround with @-signs or whatever. Or any other workaround.
You can still provide a strong clue that something might be wrong.
For example, all invalid parameters could be higlighted with
red bold. Put the cursor on a bad parameter, and a status field
could light up with a descriptive message like " 'foobar' is an
invalid/unsupported parameter" or "You need a positive number here."
Helge Hafting
