Skip to content

Conversation

@jordan-walters
Copy link

We at Chamsys/Chauvet would really benefit from the addition of a HasDefaultValue() function on the IGdtfDmxChannelFunction interface. At present 0 (zero) is returned if there is a DefaultValue set to 0, or if there is no DefaultValue. If there is no DefaultValue we would then want to assign our own default value - depending on the Channel's attribute.

My code enhancement is based on the already existing IGdtfDmxChannel HasHighlight() function.

We at Chamsys/Chauvet would really benefit from the addition of a HasDefaultValue() function on the IGdtfDmxChannelFunction interface.
At present 0 (zero) is returned if there is a DefaultValue set to 0, or if there is no DefaultValue.
If there is no DefaultValue we would then want to assign our own default value - depending on the Channel's attribute.

My code enhancement is based on the already existing IGdtfDmxChannel HasHighlight() function.
@welcome
Copy link

welcome bot commented May 21, 2025

Thanks for opening this pull request! Please check out our contributing guidelines.

Copy link
Collaborator

@AndriiVoitenko AndriiVoitenko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @jordan-walters , there is a logical difference between Highlight and Default: there are cases where Highlight from logical point of view make no sense. For example, attribute Pan, from logical point of view pan does not have Highlight value. And for such cases GDTF specification defines a special None value for Highlight xml attribute of DMX channel.

Xml attribute Default of channel function means “Default DMX value of channel function when activated by the control system”. Device can not be in undefined state, always when user activates channel function it should be in some defined state, otherwise visualizer and controller can not predict output. Therefore, Default value of Channel function is a mandatory one and can not have None as special value. And as @petrvanekrobe write you in #71, the solution is to extend specification with default for "Default" xml attribute which would be equal DMX From.

That’s why you pull request introduce a new functionality which collides with GDTF specification and can not be merged into master branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants