.asc to .asy : Parameter Editor

Hi itsko ,

I see. Solid request. A little difficult because of the legacy Attributes dialog and the interaction that would be required. A bit UI bound. You might be surprised (or not) at how hardcoded the dialogs have to be in MFC.

Maybe, as you note, the hardest part might be what happens if someone changes/adds a spiceline to the local symbol, param=blah, and the fact you can just one-line all the params: "spiceline param1=blah param2=foo param3=bar". None of that is acted on until the spiceline is written out in the netlist. Have to think about it.

mike

Like, could the Parameter Editor table:

just result in SpiceLine being prepended with the table info:

SpiceLine =
+ A=7
+ B=5
+ C=3.14
+ D=0.11
+ E={1e3}
+ F=7
+ <zzz>

where <zzz> is whatever the user manually wrote in
Params (hierarchal sheet, prefix=<blank>) or
SpiceLine (subcircuit, prefix=X)

If ltspice could easily check for duplicates between table and mask code, and
ignore writing any table parameters which are immediately overwritten in manual SpiceLine code,
even better, but if not, this would still be completely serviceable.

[If brackets shouldn't have been included in Value, please disregard.]

Hi itsko 

itsko said:

SpiceLine =
+ A=7
+ B=5
+ C=3.14
+ D=0.11
+ E={1e3}
+ F=7

Yes, very clean. UI limits how we could make this clear to the user.

itsko said:

If ltspice could easily check for duplicates between table and mask code, and
ignore writing any table parameters which are immediately overwritten in manual SpiceLine code,
even better, but if not, this would still be completely serviceable.

Also, makes sense, but would be far more difficult than it should be, believe me.

Difficulties aside, I'll put in a formal feature request, because it would be a nice feature.

mike

Ty.

[Edited original post for clarity: <zzz> ]

Would the user need to see it?

I meant if the table was used, any generation of SPICE code could potentially just pull table contents and stuff it into SpiceLine before SpiceLine was passed where it goes, or if wherever SpiceLine goes could accept newlines, using a for loop to convert each table row into

+ <param>=<value>

followed by:

+ <actual contents of SpiceLine>

might even be possible.

[I'm not a dev so I apologize for being very speculative about suggestions.]

.

If checking for duplicates would be difficult, (I can certainly imagine and believe you), then please exclude it from the feature request. It's not important.

Ty.

[Edited original post for clarity: <zzz> ]

Would the user need to see it?

I meant if the table was used, any generation of SPICE code could potentially just pull table contents and stuff it into SpiceLine before SpiceLine was passed where it goes, or if wherever SpiceLine goes could accept newlines, using a for loop to convert each table row into

+ <param>=<value>

followed by:

+ <actual contents of SpiceLine>

might even be possible.

[I'm not a dev so I apologize for being very speculative about suggestions.]

.

If checking for duplicates would be difficult, (I can certainly imagine and believe you), then please exclude it from the feature request. It's not important.