[FIX] FS Beam

emagdalenaC2i

Hi @NeilCooke

There is a small bug in the Beam FeatureScript


To fix it, just replace in the "Beam Feature" tab the line 105:

if (!definition.setCustomName)

to

else

This is the code I use:

<div>if (definition.profileType == ProfileType.CUSTOM)</div><div>{</div><div>	annotation { "Name" : "Override", "UIHint" : "REMEMBER_PREVIOUS_VALUE" }</div><div>	definition.setCustomName is boolean;</div><div>	if (definition.setCustomName)</div><div>	{</div><div>		annotation { "Name" : "Name", "Default" : "Custom Profile", "UIHint" : "REMEMBER_PREVIOUS_VALUE" }</div><div>		definition.customName is string;</div><div>	}</div><div>}</div><div>else</div><div>{</div><div>	annotation { "Name" : "Standard", "Default" : false, "UIHint" : "REMEMBER_PREVIOUS_VALUE" }</div><div>	definition.nameStandard is boolean;</div><div><br></div><div>	annotation { "Name" : "Profile", "Default" : true, "UIHint" : "REMEMBER_PREVIOUS_VALUE" }</div><div>	definition.nameProfile is boolean;</div><div>}</div>

NeilCooke

Thanks Eduardo - the standard/profile option is still required for custom profiles. If they have been tagged then this data will be used, if not, the user can override and enter a different name. 

I used:

if (definition.profileType == ProfileType.STANDARD || (definition.profileType == ProfileType.CUSTOM && !definition.setCustomName))

Feature versioned - thanks for finding this.

emagdalenaC2i

You probably like this vídeo ;-)
https://www.youtube.com/watch?v=tn3-0H63RfQ

NeilCooke

VERY NICE!!