v 4.1 March 12 2014. One of many settingDefinitions in a custom frameworksettings file. It isn't shown in the designer. Neither is in "Code gen. info" the possibility to choose a Spparameter as "Element" for setting (only the SpCall) Checked that this file is the one loading. The designer is modified accordingly. All the other settings (no spcallparameter target) shown without a single problem.

 <!-- TypedViewField + SpParameter -->
<settingDefinition name="RelatedField"  description="test"
                canBeEmpty="true" category="My Templates" type="string" targetElement="6144" />

or...

 <!-- SpParameter -->
<settingDefinition name="RelatedField"  description="test"
                canBeEmpty="true" category="My Templates" type="string" targetElement="4096" />

By the way... target types for TVFcall and TVF parameters would be welcome.

TIA

raist wrote:

It isn't shown in the designer. Neither is in "Code gen. info" the possibility to choose a Spparameter as "Element" for setting (only the SpCall)

Hi Jose. Yes you are right. We will investigate this...

There's indeed no parameter setting element, as there's little to do with a parameter in the generated code. That is... with what we ship. It's indeed a bit limiting... we'll add it in v4.2.

TvfCall is 128, TvfCallParameter is 16384. This has been the case in v4.1, as documented: http://www.llblgen.com/documentation/4.1/SDK/hh_goto.htm#definingcustomsettings.htm

So I think you mean something else?

Upps. No, that's all I wish! I checked an old version of the SDK docs, sorry. <I curse you, Google>.

BTW, Checked that there is no parameter setting element for TvfParameter in the designer, either.

Thanks.

raist wrote:

Upps. No, that's all I wish! I checked an old version of the SDK docs, sorry. <I curse you, Google>.

BTW, Checked that there is no parameter setting element for TvfParameter in the designer, either.

Thanks.

Yeah, the parameters are not used otherwise than as input arguments to a method, so specifying attributes for example has no effect.

We'll enable it for v4.2 (settings only, not attributes).