| RE: [cdt-dev] Default value for stringList |
|
What you said is not quite true. While the “default” attribute is not used, if you specify a listOptionValue for one of these types in the extension markup, it will be used to populate the default value of the option. In your example below, if you didn’t specify builtIn=true, then the values would appear in the GUI and be editable by the user.
___________________________________________
Chris Recoskie Software Designer Texas Instruments, Toronto http://eclipse.org/cdt
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Sennikovsky, Mikhail
Hi Aparna,
There is no way to mention default values for the list-type options using MBS syntax, but there is a possibility to specify built-in values, e.g.
<option name="Include Paths" command="-I" browseType="directory" valueType="includePath" id="sub.tool.opt.inc.paths"> <listOptionValue value="/usr/gnu/include" builtIn="true"> </listOptionValue> </option>
Do you need to specify default list-type values or built-ins?
Note: I suppose you should be able to specify default values for the list-type options programmatically, e.g. using value handler mechanism. What type of exception do you get when trying to set the default value from your value handler call-back?
Regards, Mikhail
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Aparna Argade
Hi, As per MBS model, stringList/ definedSymbols or similar special types do not use default value. I tried to set value through valueHandler class also, but there also exception occurs. Is there any way to mention default value for a stringList or definedSymbols? Regards, Aparna |