Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OpDialogue : Fix postExecuteBehaviour handling #6131

Merged

Conversation

ivanimanishi
Copy link
Member

This was broken by the switch to native python enums from IECore.Enum.

This commit also preserves compatibility with the old string values provided by IECore.Enum.

Note that having the Ops refer to GafferCortexUI.OpDialogue.PostExecuteBehaviour instead of hard-coded strings is not practical because that would require importing GafferCortexUI in the Op.

Checklist

  • I have read the contribution guidelines.
  • I have updated the documentation, if applicable.
  • I have tested my change(s) in the test suite, and added new test cases where necessary.
  • My code follows the Gaffer project's prevailing coding style and conventions.

This was broken by the switch to native python enums from `IECore.Enum`.

This commit also preserves compatibility with the old string values
provided by `IECore.Enum`.

Note that having the `Ops` refer to
`GafferCortexUI.OpDialogue.PostExecuteBehaviour` instead of hard-coded
strings is not practical because that would require importing
`GafferCortexUI` in the `Op`.
@johnhaddon johnhaddon merged commit a977dc9 into GafferHQ:1.5_maintenance Nov 4, 2024
5 checks passed
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