Skip to content

Allow optional/empty fields in job/pool templates #1082

@psyrus

Description

@psyrus

I'm submitting a ... (check one with "x")
[ ] bug report
[x] feature request

Description
If a field is defined as a string in the template json file, the parameter can not be left empty. With render jobs, there will be times where users wish to override the settings in the scene file (such as the currently defined height & width for the frame, but there may be times where they wish to render with the settings contained in the scene files.

Examples of things that would potentially be overridden:

This would probably necessitate a "required":"true" flag for fields, or something similar.

In the screenshot below, the user wanted to override the output type to be EXR, but wished to not have to specifically define the camera (might involve opening up the scene and typing out a cryptically named camera name with a chance for a typo)... but leaving it blank to use the scene default is currently not possible (it seems).

bl-custom-fields

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions