Skip to main content
Richard Rosenman
Inspiring
January 6, 2024
Answered

Arbitrary Parameter Not Respecting CANNOT_TIME_VARY and COLLAPSE_TWIRL

  • January 6, 2024
  • 1 reply
  • 238 views

Hi gang;

 

I've got an Arbitrary custom parameter which I've assigned the flags (among others):

PF_ParamFlag_CANNOT_TIME_VARY

And

PF_ParamFlag_COLLAPSE_TWIRLY;

 

With the arb parameter, I understand these go within the function body like so:

 

PF_ADD_ARBITRARY2("Custom Parameter",
	UI_BOX_WIDTH,
	UI_BOX_HEIGHT,
	0,
	PF_PUI_CONTROL | PF_PUI_DONT_ERASE_CONTROL | PF_ParamFlag_CANNOT_TIME_VARY | PF_ParamFlag_COLLAPSE_TWIRLY,
	def.u.arb_d.dephault,
	PARAM_DISK_ID,
	ARB_REFCON);

 

However, the keyframing icon still appears and the parameter twirl still defaults to open. CANNOT_TIME_VARY should make the parameter non-keyframable and COLLPASE_TWIRL should start the parameter closed.

 

Are there different flags that should be used to achieve this with arbitrary parameters?

 

Thanks,

-Richard

This topic has been closed for replies.
Correct answer shachar carmi

you put it in the wrong place. it belongs one arg before, where now there's a 0.

the previous arg is the param flags, and you put in the param *UI* flags.

1 reply

shachar carmiCommunity ExpertCorrect answer
Community Expert
January 7, 2024

you put it in the wrong place. it belongs one arg before, where now there's a 0.

the previous arg is the param flags, and you put in the param *UI* flags.