[EMAIL PROTECTED] wrote:
If you look at InsetCommandParams, you'll see that params_ is set in
read(), and the other InsetCommand derived insets call read() when they
need to set params_. (When they need to read the params, they just get
params_ directly via params() and index into it.) That's what I meant
when
I said that using [gs]etOptions is an older way of doing this.
I know what you mean. When you have a string, you can use read(Lexer)
to set params_. But if you have a InsetCommandParams, setOption is the
only way to set params_ of it... maybe I am wrong here.
I *think* the way to do this is:
string const paramStr = InsetIncludeMailer::params2string(params_);
params_.read(paramStr);
Abdel...is this right, more or less?
Looks so yes.
For what it's worth, I find the indirection through a string kind of
annoying. (This has been discussed before.) But that's how it's set up at
the moment.
And I agree with you ;-) but we agreed with Georg to discuss that matter
later.
Abdel.
