[osg-submissions] osgconv: changes to handling of command line options

[Robert Osfield]

Hi Max,

On 8/20/07, Max Langbein <m_langbe at informatik.uni-kl.de> wrote:
> On Sun, 19 Aug 2007, Robert Osfield wrote:
>
> > Hi Max,
> >
> > This is not an appropriate change as it'll eat command line entries
> > that might not be intended to be part of the option string.
>
> I think that is exactly what the current code does: eat up all options
> with -O and pass only the last one to the Reader/Writer Plugin.

I've just re-read your emails and reviewed the existing code in the
OSG and now understand better what you are trying to fix.  My
suggestion of using :

 osgconv -O "PRECISION 10" bplan_from3ds.dxf

Is exactly what you should be doing at your end, and this is how it is
meant to be used and how users have been using it over the years and
why others haven't had the same problem as you.

What should happen when parsing the option string should probably be
to parse it along with the command line parameters such that they are
inherited from the left to right i.e.

 osgconv -O "options 1" myfile.fmt -O "option 2" mysecondfile.fmt

Having multiple -O entries per file is something that could still be
supported, although its a bit backward considering its much easier and
less ambiguous to just put quotes around a single -O entry.

Robert.