Change .OPTIONS and .FUNC components to allow free editing of contents.

[iwbnwif]

Potential fix for #1260.

[iwbnwif]

I have assumed that these dialogs should not have the "Simulation" and "Put result in dataset" options.

[ra3xdh]

I have assumed that these dialogs should not have the "Simulation" and "Put result in dataset" options.

Yes, the both components should not have these properties.

The .OPTIONS has another problem. The first property of this component XyceOptionPackage should be excluded from the free editing. It is unclear how to process this device with the new dialog. The solution may be to put a QLineEdit holding the first property. The disadvantage of this solution is that it serves only for .OPTIONS device.

[iwbnwif]

Please can you point me any docs on the function of XyceOptionPackage and how it affects the simukation or other options.

One solution might be to create a separate component that holds this value pair. This has the advantage of only being visible in the pallette (and greyed in the schematic) when Xyce is active as the simulation engine.

[ra3xdh]

The usage of .OPTIONS could be found in Xyce Reference guide, chapter 2.1.25 https://xyce.sandia.gov/files/xyce/Xyce_Reference_Guide_7.6.pdf

I am considering to deprecate the both .OPTIONS and .FUNC components as redundant. After introduction of free editing the purpose of these devices is duplicated by include script.

[iwbnwif]

Thank you for the link.

Sorry, I am missing the problem here. If I enter the following in the Options dialog, a valid netlist appears to be generated. Unfortunately, my Xyce installation is broken at the moment, so I can't test if it actually simulates.

Netlist snip:

.PARAM dBS21={dB(S[2,1])}
.PARAM dBS11={dB(S[1,1])}
.OPTIONS TIMEINT  ABSTOL = 1E-8 

So the netlist appears to be the same as the example in the Xyce reference guide section 2.1.25.

[ra3xdh]

Sorry, I am missing the problem here.

The user may modify the name (XyceOptionPackage) of the first property or event delete the first property by accident. The netlist will be wrong in such case. The first property should be with fixed name and always present. The solution may be to add validation and warning if the user press OK. The validation must be done only for .OPTIONS device.

[iwbnwif]

Thank you for the explanation. It may be a few days before I can look at this again but hopefully that isn't too inconvenient as there is a workaround.