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

Natron : Bug About DropDownList of Input and Output Colorspace #22

Closed
Francois-Grassard opened this issue Jun 23, 2014 · 3 comments
Closed
Milestone

Comments

@Francois-Grassard
Copy link

Hi,

The first time i launched Natron, I add a Read node and source a PNG files sequence.
At first, I forgot to set a OCIO config file. Because of that, Input and Output Colorspace wasn't two dropdownlist, but two blank edit text field. I type some junk into those lines and press "enter". Natron tell me that it was an error, I press OK and suddenly the dropdownlist appeared. I did it once more for the second line ... and the second dropdownlist was there.

I think it could be interesting to have blank dropdownlist at start, with a warning message about the missing OCIO configuration file. :o)

Thanks !

Francois 'CoyHot' Grassard

@Francois-Grassard Francois-Grassard changed the title Natron : Bug Natron : Bug About DropDownList of Input and Output Colorspace Jun 23, 2014
@devernay devernay added the bug label Jun 24, 2014
@devernay
Copy link
Collaborator

The editable fields are for compatibility with other hosts, which cannot modify the option lists.
Can you give more details to help reproducing the bug (platform, version)?
The bug may be in matron or in openfx-io

@MrKepzie
Copy link
Owner

This behaviours occurs when no ocio config can be found. You have to click once in the string param to get a dialog warning the config doesn't exist, and then a second time to pop the combo box.

@devernay devernay added this to the 1.0 milestone Jun 24, 2014
@devernay devernay added invalid and removed bug labels Jul 5, 2014
@devernay
Copy link
Collaborator

devernay commented Jul 5, 2014

I guess this is not a bug anymore?

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

No branches or pull requests

3 participants